public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: Roland Schwingel <roland.schwingel@onevision.de>, gdb@sourceware.org
Subject: Re: Stack unwinding on Windows  with gdb 6.x (was: gdb stack trace problems (Addendum))
Date: Tue, 17 May 2005 16:58:00 -0000	[thread overview]
Message-ID: <20050517165605.GF12869@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4289AD9E.7060206@onevision.de>

On Tue, May 17, 2005 at 10:38:54AM +0200, Roland Schwingel wrote:
>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?

I use gdb to debug on Windows on a daily basis and I don't find myself
hampered by gdb's inability to backtrace out of system functions.  It's
ability to do that has always been iffy.

So, as the windows maintainer, I have no immediate plans to try to
address this.  If it is bothering you, however, then I'll certainly
review any patches that you submit.

cgf

  reply	other threads:[~2005-05-17 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  8:40 Roland Schwingel
2005-05-17 16:58 ` Christopher Faylor [this message]
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=20050517165605.GF12869@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --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).