From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Problem with new step-bt test?
Date: Thu, 10 Aug 2006 00:28:00 -0000 [thread overview]
Message-ID: <20060810002802.GA5465@nevyn.them.org> (raw)
In-Reply-To: <20060809234006.GU1385@adacore.com>
On Wed, Aug 09, 2006 at 04:40:06PM -0700, Joel Brobecker wrote:
> printed if we're "inside" a line of code, right? After a step or two,
> we should be still inside the prologue, so I figured we should see
> them printed.
That's the faulty assumption: prologues can be pretty short, in fact.
> I can do that sometime later tonight.
Thanks!
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-08-10 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 22:05 Daniel Jacobowitz
2006-08-09 23:40 ` Joel Brobecker
2006-08-10 0:28 ` Daniel Jacobowitz [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=20060810002802.GA5465@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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