Remove trailing white spaces in gdb/frame.{c,h}

gdb/ChangeLog:

	* frame.c: Remove trailing white spaces.
	* frame.h: Likewise.
This commit is contained in:
Shahab Vahedi
2020-12-22 18:08:41 +01:00
parent acf10cacc6
commit e512699ac8
3 changed files with 13 additions and 8 deletions

View File

@ -1,3 +1,8 @@
2020-12-22 Shahab Vahedi <shahab@synopsys.com>
* frame.c: Remove trailing white spaces.
* frame.h: Likewise.
2020-12-22 Shahab Vahedi <shahab@synopsys.com> 2020-12-22 Shahab Vahedi <shahab@synopsys.com>
* arc-linux-tdep.c: Replace "regnum" with "REGNUM" in comments. * arc-linux-tdep.c: Replace "regnum" with "REGNUM" in comments.

View File

@ -2250,7 +2250,7 @@ get_prev_frame_always_1 (struct frame_info *this_frame)
CORE_ADDR this_pc_in_block; CORE_ADDR this_pc_in_block;
struct minimal_symbol *morestack_msym; struct minimal_symbol *morestack_msym;
const char *morestack_name = NULL; const char *morestack_name = NULL;
/* gcc -fsplit-stack __morestack can continue the stack anywhere. */ /* gcc -fsplit-stack __morestack can continue the stack anywhere. */
this_pc_in_block = get_frame_address_in_block (this_frame); this_pc_in_block = get_frame_address_in_block (this_frame);
morestack_msym = lookup_minimal_symbol_by_pc (this_pc_in_block).minsym; morestack_msym = lookup_minimal_symbol_by_pc (this_pc_in_block).minsym;
@ -2518,9 +2518,9 @@ get_prev_frame (struct frame_info *this_frame)
pcsqh register (space register for the instruction at the head of the pcsqh register (space register for the instruction at the head of the
instruction queue) cannot be written directly; the only way to set it instruction queue) cannot be written directly; the only way to set it
is to branch to code that is in the target space. In order to implement is to branch to code that is in the target space. In order to implement
frame dummies on HPUX, the called function is made to jump back to where frame dummies on HPUX, the called function is made to jump back to where
the inferior was when the user function was called. If gdb was inside the inferior was when the user function was called. If gdb was inside
the main function when we created the dummy frame, the dummy frame will the main function when we created the dummy frame, the dummy frame will
point inside the main function. */ point inside the main function. */
if (this_frame->level >= 0 if (this_frame->level >= 0
&& get_frame_type (this_frame) == NORMAL_FRAME && get_frame_type (this_frame) == NORMAL_FRAME
@ -2565,7 +2565,7 @@ get_prev_frame (struct frame_info *this_frame)
That should provide a far better stopper than the current That should provide a far better stopper than the current
heuristics. */ heuristics. */
/* NOTE: tausq/2004-10-09: this is needed if, for example, the compiler /* NOTE: tausq/2004-10-09: this is needed if, for example, the compiler
applied tail-call optimizations to main so that a function called applied tail-call optimizations to main so that a function called
from main returns directly to the caller of main. Since we don't from main returns directly to the caller of main. Since we don't
stop at main, we should at least stop at the entry point of the stop at main, we should at least stop at the entry point of the
application. */ application. */
@ -2600,7 +2600,7 @@ get_prev_frame_id_by_id (struct frame_id id)
{ {
struct frame_id prev_id; struct frame_id prev_id;
struct frame_info *frame; struct frame_info *frame;
frame = frame_find_by_id (id); frame = frame_find_by_id (id);
if (frame != NULL) if (frame != NULL)

View File

@ -149,8 +149,8 @@ struct frame_id
/* The frame's special address. This shall be constant through out the /* The frame's special address. This shall be constant through out the
lifetime of the frame. This is used for architectures that may have lifetime of the frame. This is used for architectures that may have
frames that do not change the stack but are still distinct and have frames that do not change the stack but are still distinct and have
some form of distinct identifier (e.g. the ia64 which uses a 2nd some form of distinct identifier (e.g. the ia64 which uses a 2nd
stack for registers). This field is treated as unordered - i.e. will stack for registers). This field is treated as unordered - i.e. will
not be used in frame ordering comparisons. not be used in frame ordering comparisons.