From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Minor reformatting in infrun.c
Date: Fri, 16 Aug 2002 17:18:00 -0000 [thread overview]
Message-ID: <20020817001848.GX906@gnat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
I am about to touch this part of the code, and it needed a bit of
reformatting, so I thought I'd commit the reformatting separately.
2002-08-16 Joel Brobecker <brobecker@gnat.com>
* infrun.c (handle_inferior_event): Minor reformatting, to make
a rather long condition expression easier to read.
--
Joel
[-- Attachment #2: infrun.c.diff --]
[-- Type: text/plain, Size: 2261 bytes --]
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.65
diff -c -3 -p -r1.65 infrun.c
*** infrun.c 16 Aug 2002 17:56:17 -0000 1.65
--- infrun.c 16 Aug 2002 23:57:51 -0000
*************** handle_inferior_event (struct execution_
*** 2106,2125 ****
singlestepping a trap instruction, and singlestepping thru a
jump to the instruction following a trap instruction. */
! stop_bpstat = bpstat_stop_status (&stop_pc,
! /* Pass TRUE if our reason for stopping is something other
! than hitting a breakpoint. We do this by checking that
! 1) stepping is going on and 2) we didn't hit a breakpoint
! in a signal handler without an intervening stop in
! sigtramp, which is detected by a new stack pointer value
! below any usual function calling stack adjustments. */
! (currently_stepping (ecs)
! && prev_pc !=
! stop_pc - DECR_PC_AFTER_BREAK
! && !(step_range_end
! && INNER_THAN (read_sp (),
! (step_sp -
! 16)))));
/* Following in case break condition called a
function. */
stop_print_frame = 1;
--- 2106,2124 ----
singlestepping a trap instruction, and singlestepping thru a
jump to the instruction following a trap instruction. */
! stop_bpstat =
! bpstat_stop_status
! (&stop_pc,
! /* Pass TRUE if our reason for stopping is something other
! than hitting a breakpoint. We do this by checking that
! 1) stepping is going on and 2) we didn't hit a breakpoint
! in a signal handler without an intervening stop in
! sigtramp, which is detected by a new stack pointer value
! below any usual function calling stack adjustments. */
! (currently_stepping (ecs)
! && prev_pc != stop_pc - DECR_PC_AFTER_BREAK
! && !(step_range_end
! && INNER_THAN (read_sp (), (step_sp - 16)))));
/* Following in case break condition called a
function. */
stop_print_frame = 1;
next reply other threads:[~2002-08-17 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 17:18 Joel Brobecker [this message]
2002-08-16 19:48 ` Michael Snyder
2002-08-22 16:52 ` Joel Brobecker
2002-08-22 18:25 ` Michael Snyder
2002-08-23 10:29 ` Joel Brobecker
2002-08-23 11:31 ` Michael Snyder
2002-08-23 15:06 ` Joel Brobecker
2002-08-23 15:23 ` Andrew Cagney
2002-08-23 16:15 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020817001848.GX906@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox