Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Roland Schwingel <roland.schwingel@onevision.de>
To: Pedro Alves <pedro@codesourcery.com>, gdb <gdb@sourceware.org>
Subject: Re: Strange stack trace on Windows
Date: Tue, 17 Mar 2009 15:26:00 -0000	[thread overview]
Message-ID: <49BFC113.3070102@onevision.de> (raw)

Hi Pedro...

Thanks for your reply.

Pedro Alves wrote on 17.03.2009 15:27:09:
 > On Tuesday 17 March 2009 13:48:24, Roland Schwingel wrote:
 > > It is quite painful to use gdb on windows for quite a while now.
 > > Windows, whether one may like it or not, is a major platform
 > > and gdb should also operate well here. I am fighting for a long time
 > > with these problems now. Isn't there a general solution thinkable?
 >
 > Sure there is.  :-)  Teach GDB about MSFT's debug info, e.g., PDB files,
 > and about the FPO (frame pointer omission) information in them.
 >
 > See e.g., <http://www.debuginfo.com/articles/gendebuginfo.html>.
Sigh... This is the answer I have feared. If one would do that he
must also implement that as kind of multi debug format handling.
The code which is compiled with gcc and having stabs(or dwarf2)
debugging informations and the system shared libs having MS
format..

Maybe someone has to take this challenge once...

Roland


             reply	other threads:[~2009-03-17 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 15:26 Roland Schwingel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-23 13:12 Roland Schwingel
2009-03-18  9:26 Roland Schwingel
2009-03-19 14:18 ` Joel Brobecker
2009-03-17 15:39 Roland Schwingel
2009-03-17 19:43 ` Joel Brobecker
2009-03-17 13:49 Roland Schwingel
2009-03-17 14:27 ` Pedro Alves
2009-03-17 15:08 ` Joel Brobecker
2009-03-17 11:58 Roland Schwingel
2009-03-17 13:19 ` Joel Brobecker
2007-09-29 22:01 Gordon Prieur
2007-09-30  3:00 ` Daniel Jacobowitz
2007-09-30 18:13 ` Eli Zaretskii
2007-10-01 14:03   ` Gordon Prieur
2007-10-01 14:39     ` Joel Brobecker

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=49BFC113.3070102@onevision.de \
    --to=roland.schwingel@onevision.de \
    --cc=gdb@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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