From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] problem fetching inferior memory due to breakpoint
Date: Thu, 27 Apr 2006 20:28:00 -0000 [thread overview]
Message-ID: <u3bfyhifo.fsf@gnu.org> (raw)
In-Reply-To: <20060426190517.GA930@adacore.com> (message from Joel Brobecker on Wed, 26 Apr 2006 12:05:17 -0700)
> Date: Wed, 26 Apr 2006 12:05:17 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> Break at the first instruction of hello(), and then do a couple of
> stepi's:
>
> (gdb) b *hello
> Breakpoint 1 at 0x401050: file foo.c, line 5.
> (gdb) run
> Starting program: /[...]/foo.exe
>
> Breakpoint 1, hello () at foo.c:5
> 5 {
> (gdb) stepi
> 0x00401051 5 {
> (gdb) bt
> #0 0x00401051 in hello () at foo.c:5
> #1 0x00401093 in main () at foo.c:12
> (gdb) stepi
> 0x00401053 in hello () at foo.c:5
> 5 {
>
> So we're at the third instruction of the function. Here is the backtrace
> we get when I request it:
>
> (gdb) bt
> #0 0x00401053 in hello () at foo.c:5
> #1 0x0022ee88 in ?? ()
> #2 0x00401093 in main () at foo.c:12
>
> We get an extra frame between hello() and main().
I cannot reproduce this with a MinGW-compiled program, using GDB 6.3
and 6.3.50.20051116-cvs. What version of GDB are you using? Is this
problem visible only in a recent codebase?
next prev parent reply other threads:[~2006-04-27 20:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 19:05 Joel Brobecker
2006-04-26 19:19 ` Daniel Jacobowitz
2006-04-26 21:18 ` Joel Brobecker
2006-04-26 21:39 ` Daniel Jacobowitz
2006-04-26 22:18 ` Joel Brobecker
2006-04-26 22:29 ` Daniel Jacobowitz
2006-04-26 23:33 ` Michael Snyder
2006-04-27 0:42 ` Daniel Jacobowitz
2006-04-27 1:37 ` Michael Snyder
2006-04-27 2:10 ` Daniel Jacobowitz
2006-04-27 0:53 ` Jim Blandy
2006-04-27 20:28 ` Eli Zaretskii [this message]
2006-04-27 20:56 ` Joel Brobecker
2006-04-28 5:12 ` Eli Zaretskii
2006-04-28 17:00 ` Joel Brobecker
2006-04-28 17:45 ` Daniel Jacobowitz
2006-04-29 14:14 ` Eli Zaretskii
2006-04-29 14:14 ` Eli Zaretskii
2006-04-29 14:20 ` Daniel Jacobowitz
2006-04-29 14:48 ` Eli Zaretskii
2006-04-29 15:06 ` Daniel Jacobowitz
2006-04-29 15:18 ` Daniel Jacobowitz
2006-04-29 17:10 ` Eli Zaretskii
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=u3bfyhifo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.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