From: Andrew Cagney <cagney@gnu.org>
To: Matt Fyles <mattf@clearspeed.com>
Cc: gdb@sources.redhat.com
Subject: Re: Stepping through code with breakpoints on adjacent address lines.
Date: Mon, 31 Jan 2005 16:43:00 -0000 [thread overview]
Message-ID: <41FE6005.5050003@gnu.org> (raw)
In-Reply-To: <JAEHKFDEOPCKGLEGDENFAEOMCBAA.mattf@clearspeed.com>
Matt Fyles wrote:
> I just wanted to clear up the expected behavior when stepping code that has
> breakpoints on adjacent address lines.
>
> In this simple example.
>
> 0x0 instruction A
> 0x4 instruction B
> 0x8 instruction C
>
> If I break on addresses 0x0, 0x4 and 0x8 with the break *(address)
> functionality and then continue to 0x0 and step the other 2 instructions I
> only ever see the breakpoint trigger on address 0x0. GDB steps to the next 2
> addresses but does not report a breakpoint at either location. Is this the
> expected behavior.
>
> It looks from the source in infrun.c (handle_inferior_event()) that if the
> trap_expected flag is set then it discards any breakpoint matching at the
> current address.
Smells like a broken edge case. Here's similar equally wierd behavior:
(top-gdb) info break
Num Type Disp Enb Address What
4 breakpoint keep y 0x1004e83c in main
at
/home/scratch/GDB/src/gdb/gdb.c:30
breakpoint already hit 1 time
5 breakpoint keep y 0x1004e83c in main
at
/home/scratch/GDB/src/gdb/gdb.c:31
breakpoint already hit 1 time
6 breakpoint keep y 0x1004e844 in main
at
/home/scratch/GDB/src/gdb/gdb.c:33
7 breakpoint keep y 0x1004e840 in main
at
/home/scratch/GDB/src/gdb/gdb.c:32
8 breakpoint keep y 0x1004e84c in main
at
/home/scratch/GDB/src/gdb/gdb.c:34
breakpoint already hit 1 time
((top-gdb) run
Breakpoint 4, main (argc=0x1, argv=0x7ffff954)
at /home/scratch/GDB/src/gdb/gdb.c:31
31 args.argc = argc;
(top-gdb) s
32 args.argv = argv;
(top-gdb)
33 args.use_windows = 0;
(top-gdb)
Breakpoint 8, main (argc=0x1, argv=0x7ffff954)
at /home/scratch/GDB/src/gdb/gdb.c:34
34 args.interpreter_p = INTERP_CONSOLE;
(top-gdb) info break
Would you be able to come up with an automated testcase?
Andrew
prev parent reply other threads:[~2005-01-31 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 9:28 Matt Fyles
2005-01-31 16:43 ` Andrew Cagney [this message]
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=41FE6005.5050003@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mattf@clearspeed.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