From: Roland Schwingel <roland.schwingel@onevision.de>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sourceware.org
Subject: Re: gdb stack trace problems (Addendum)
Date: Tue, 10 May 2005 08:38:00 -0000 [thread overview]
Message-ID: <428072D8.80102@onevision.de> (raw)
Hi...
Mark Kettenis wrote on 08.05.2005 15:30:20:
> Date: Mon, 02 May 2005 09:03:08 +0200
> From: Roland Schwingel <roland.schwingel@onevision.de>
>
> Hi Mark...
>
> Have you already had some time to look into my results with your
patch to
> the i386 stack unwinder? At basically it could work but obviously it
> is not advancing to the next stack frame... Attached you will find my
> results
>
> This isn't very encouraging. My approach obviously isn't working very
> well. My suggestion is to go for a Windows-specific solution, where
> one would use a special unwinder for the sort of undebuggable code
> that's found in the Windows system DLLs. But I'm afraid I can't
> really do much since I don't have a Windows system. Chris, is there
> any change you can hack something like this into i386-cygwin-tdep.c?
Uff.... Sad to hear...
Roland
next reply other threads:[~2005-05-10 8:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 8:38 Roland Schwingel [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-10 8:39 Roland Schwingel
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
2005-05-09 5:30 ` Stan Shebs
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=428072D8.80102@onevision.de \
--to=roland.schwingel@onevision.de \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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).