Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Roland Schwingel <roland.schwingel@onevision.de>
To: gdb@sourceware.org
Subject: Stack unwinding on Windows  with gdb 6.x (was: gdb stack trace problems (Addendum))
Date: Tue, 17 May 2005 08:40:00 -0000	[thread overview]
Message-ID: <4289AD9E.7060206@onevision.de> (raw)

Hi...

I don't like to reply to my own messages but I don't want to let this
to be fallen asleep again. In my eyes gdb 6.x is at present only of
very limited use when debugging on windows mingw compiled
executables because it cannot dump stack frames reliable.

I know that the stack unwinder of gdb 6.x is of much better
nature then the one of 5.3, but with 5.3 one could use gdb
very good on windows to debug mingw code.

So I think gdb 6.x should be able again to work on
windows. So what can be done to fix this?

Are there any pointers to find out how the current
stack unwinder works compared to the old one. Maybe
it would be possible to mix the 2 on windows.

Thanks,

Roland


             reply	other threads:[~2005-05-17  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  8:40 Roland Schwingel [this message]
2005-05-17 16:58 ` Christopher Faylor
2005-05-18  8:08 Roland Schwingel

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=4289AD9E.7060206@onevision.de \
    --to=roland.schwingel@onevision.de \
    --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