From: Daniel Jacobowitz <drow@false.org>
To: Roland Schwingel <roland.schwingel@onevision.de>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: gdb stack trace problems
Date: Sat, 16 Apr 2005 14:09:00 -0000 [thread overview]
Message-ID: <20050416140949.GA542@nevyn.them.org> (raw)
In-Reply-To: <425FD85D.1060201@onevision.de>
On Fri, Apr 15, 2005 at 05:06:05PM +0200, Roland Schwingel wrote:
> Hi....
>
> At present we are suffering from stack trace problems with recent
> versions of gdb.
> I desperately hope someone knows a reason for it and can help.
>
> But from the beginning:
> We are using gdb on cygwin to debug mingw programs. GDB works well but
> in recent
> version (starting with 6.x) it cannot produce correct stack dumps
> anymore when something
> has crashed. Our applications are multithreaded.
>
> In the past we used 5.3 which worked much better in that case but had
> other problems.
> We switched a while ago to 6.2 and then to 6.2.1 and today I compiled
> 6.3.50 from CVS.
> And it is all the same... When I get a crash I just get corrupted stacks
> telling nothing useful.
>
> Does anyone know what is the reason for this and how to fix it?
Sorry, but you haven't given us any information to answer your question
with. Test case? Compiler version? Example?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-16 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 15:06 Roland Schwingel
2005-04-16 14:09 ` Daniel Jacobowitz [this message]
2005-04-18 13:48 Roland Schwingel
2005-04-18 13:57 ` Daniel Jacobowitz
2005-04-18 17:11 ` Mark Kettenis
2005-04-19 6:58 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=20050416140949.GA542@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--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