From: Christopher Faylor <me@cgf.cx>
To: roland.schwingel@onevision.de, gdb@sourceware.org,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: gdb stack trace problems (Addendum)
Date: Mon, 09 May 2005 05:26:00 -0000 [thread overview]
Message-ID: <20050509052559.GA15582@trixie.casa.cgf.cx> (raw)
In-Reply-To: <01c55452$Blat.v2.4$03d6fe00@zahav.net.il>
On Mon, May 09, 2005 at 07:45:05AM +0300, Eli Zaretskii wrote:
>> Date: Sun, 8 May 2005 19:19:53 -0400
>> From: Christopher Faylor <me@cgf.cx>
>>
>> What kind of windows-specific solution do you have in mind? How would
>> you know what to unwind? You could potentially figure out that you're
>> stuck in a system function but that doesn't mean that you know the
>> state of the stack.
>>
>> If a function doesn't set up a frame pointer and there is no debugging
>> information available, how would one derive a stack frame? I could
>> imagine a really complicated "search the stack" technique but I can't
>> see how it would ever be foolproof.
>
>Does the MSVC debugger manage to display a sensible backtrace in this
>case? If it does not, we don't need to worry, I think.
Possibly. They may have some separate debugging symbol files available
for system DLLs. I'm not extremely interested in making gdb understand
native MSVC debugging format though.
>If it does, then perhaps teh frameless functions in system DLLs follow
>some pattern in their prologue that could help us? Or perhaps they
>save stack-related info in some Windows-specific place?
I've never noticed anything special on the stack or in the assembly
language. I'm not 100% sure that the system functions are written
in C.
cgf
next prev parent reply other threads:[~2005-05-09 5:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 7:04 Roland Schwingel
2005-05-08 13:31 ` Mark Kettenis
2005-05-08 23:20 ` Christopher Faylor
2005-05-09 4:48 ` Eli Zaretskii
2005-05-09 5:26 ` Christopher Faylor [this message]
2005-05-09 5:30 ` Stan Shebs
-- strict thread matches above, loose matches on Subject: below --
2005-05-10 8:39 Roland Schwingel
2005-05-10 8:38 Roland Schwingel
2005-04-26 11:53 Roland Schwingel
2005-04-26 9:11 Roland Schwingel
2005-04-25 8:00 Roland Schwingel
2005-04-25 12:35 ` Roland Schwingel
2005-04-25 19:35 ` Mark Kettenis
2005-04-25 19:45 ` Daniel Jacobowitz
2005-04-25 20:37 ` Mark Kettenis
2005-04-19 8:01 Roland Schwingel
[not found] ` <4268B942.5080300@onevision.de>
2005-04-22 17:51 ` Mark Kettenis
2005-04-19 7:34 Roland Schwingel
2005-04-19 7:45 ` Mark Kettenis
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=20050509052559.GA15582@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=roland.schwingel@onevision.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).