public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Roland Schwingel <roland.schwingel@onevision.de>
To: Christopher Faylor <me@cgf.cx>
Cc: gdb@sourceware.org
Subject: Re: Stack unwinding on Windows  with gdb 6.x (was: gdb stack trace problems (Addendum))
Date: Wed, 18 May 2005 08:08:00 -0000	[thread overview]
Message-ID: <428AF788.5080603@onevision.de> (raw)

Hi...

Christopher Faylor wrote on 17.05.2005 18:56:05:
[...]
 > 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.
Well we are working on highly multithreaded applications and with all
that native windows thread handling you always run into these problems
with gdb 6.x. Especially when your try to track down a crash it is terrible.
You won't get *any* useful stack trace.  Whereas it was possible
with 5.3.
 
 > 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.
Thanks. I am definitely willing to do something on it but if I can get
some pointers on how stack tracing works in gdb 6.x compared
to 5.3 this would be extremely helpful.

As of the fact that I am at present extremly busy with other things
it can take until june until I can actively work on it, but when I have
some pointers where I can read on how it internally works in gdb
I already can make myself a bit more used to the internals of gdb.

Roland

             reply	other threads:[~2005-05-18  8:08 UTC|newest]

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

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=428AF788.5080603@onevision.de \
    --to=roland.schwingel@onevision.de \
    --cc=gdb@sourceware.org \
    --cc=me@cgf.cx \
    /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).