From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Wiljan Derks <Wiljan.Derks@zonnet.nl>,
gdb@sourceware.org, Mark Kettenis <kettenis@gnu.org>
Subject: Re: How to tell gdb about dlls using remote protocol
Date: Thu, 01 Feb 2007 22:54:00 -0000 [thread overview]
Message-ID: <20070201225437.GA13740@nevyn.them.org> (raw)
In-Reply-To: <20070201175311.GG17864@adacore.com>
On Thu, Feb 01, 2007 at 09:53:11AM -0800, Joel Brobecker wrote:
> This makes me wonder how well the debugger can work in certain
> situations like when backtracing from DLL code. If the debugger
> doesn't know where it is, then it's probably let to prologue analysis
> to do the unwinding. Except that it cannot determine where the prologue
> is... In that case, I see that the i386 unwinder assumes that the frame
> base can be deduced from the SP and the SP offset. Unfortunately,
> this SP offset can only be deduced from prologue analysis. Catch 22?
In general, if we can not find the start of the current function,
we have absolutely no chance of getting out of it.
This is a standard problem e.g. with the Windows system DLLs, since
we have inadequate means to recover symbol information from them.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-01 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 21:08 Wiljan Derks
2007-01-31 22:31 ` Daniel Jacobowitz
2007-02-01 17:52 ` Joel Brobecker
2007-02-01 22:54 ` Daniel Jacobowitz [this message]
2007-02-01 23:02 ` Joel Brobecker
2007-02-01 23:59 ` Daniel Jacobowitz
2007-02-02 6:20 ` Robert Dewar
2007-02-02 11:43 ` Daniel Jacobowitz
2007-02-02 16:51 ` Joel Brobecker
2007-02-02 16:56 ` Daniel Jacobowitz
2007-02-02 17:34 ` Joel Brobecker
2007-02-05 20:34 ` Wiljan Derks
2007-02-05 21:21 ` Joel Brobecker
2007-02-07 21:47 ` Mark Kettenis
2007-02-07 22:14 ` Mark Kettenis
2007-02-07 22:17 ` Daniel Jacobowitz
2007-02-08 21:14 ` Mark Kettenis
2007-02-08 23:00 ` Daniel Jacobowitz
2007-02-14 8:51 ` Joel Brobecker
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=20070201225437.GA13740@nevyn.them.org \
--to=drow@false.org \
--cc=Wiljan.Derks@zonnet.nl \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=kettenis@gnu.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