From: Tristan Gingold <gingold@adacore.com>
To: Chris Sutcliffe <ir0nh34d@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: pc 0x25c9b0 in read in psymtab, but not in symtab
Date: Fri, 08 Jan 2010 15:55:00 -0000 [thread overview]
Message-ID: <D2D25486-F2B8-4A3B-B43E-BE5130832D26@adacore.com> (raw)
In-Reply-To: <2bf229d31001080742r528ff3yba7b1e2c6de6292c@mail.gmail.com>
On Jan 8, 2010, at 4:42 PM, Chris Sutcliffe wrote:
>> yes this bug I encounter some time ago, too. It is related to DLL files
>> not having any debugging information but are shown in backtrace. Here it
>> warns once about psymtab != symtab and code in gdb fix it afterwards. IMHO
>> this warning is simply pretty bogus here, or the DLL loader should
>> generate for pe-coff the symtab, too.
>
> Hopefully this is helpful.
Not that much. This doesn't sound coherent to me because if there is no debugging information both the
psymtab and the symtab should be empty.
> If there is anything else I can do to help track down the bug, please
> let me know.
It would be nice to have a reproducer. It doesn't need to be small and I think sources are not needed
to investigate this issue.
Sadly, without reproducer I won't get far.
Tristan.
next prev parent reply other threads:[~2010-01-08 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 14:58 Elmenthaler, Jens
2010-01-08 11:41 ` Chris Sutcliffe
2010-01-08 11:46 ` Tristan Gingold
2010-01-08 11:51 ` Chris Sutcliffe
2010-01-08 11:55 ` Tristan Gingold
2010-01-08 12:02 ` Elmenthaler, Jens
2010-01-08 15:42 ` Chris Sutcliffe
2010-01-08 15:55 ` Tristan Gingold [this message]
2010-01-08 16:32 ` Elmenthaler, Jens
2010-01-11 8:46 ` Elmenthaler, Jens
2010-01-08 20:56 ` Chris Sutcliffe
2010-01-10 2:41 ` Chris Sutcliffe
2010-01-11 8:59 ` Tristan Gingold
2010-01-12 8:19 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=D2D25486-F2B8-4A3B-B43E-BE5130832D26@adacore.com \
--to=gingold@adacore.com \
--cc=gdb@sourceware.org \
--cc=ir0nh34d@gmail.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