From: Daniel Jacobowitz <drow@false.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.1.1 (PPC) crash (long)
Date: Tue, 07 Sep 2004 17:02:00 -0000 [thread overview]
Message-ID: <20040907170233.GA8073@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20040907170934.01d457f8@NT_SERVER>
On Tue, Sep 07, 2004 at 05:13:41PM +0200, Fabian Cenedese wrote:
>
> >> >Here's what happens:
> >> >
> >> >(gdb) ptype this
> >> >type = class CMainTask : public CINOSTask {
> >> > public:
> >> > CMainTask & operator=(CMainTask const &);
> >> > virtual ~CMainTask(void);
> >> > 2 [main] gdb 2100 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
> >> > 329 [main] gdb 2100 open_stackdumpfile: Dumping stack trace to gdb.exe.stackdump
> >>
> >> If anybody is interested in solving this, I can send a small debug-only file
> >> (objcopy --only-keep-debug, ~250KB) and the sources and the processed
> >> Assembler files (gcc -S). I still can't find how to solve this, debugging via
> >> gdb is quite new to me.
> >
> >I'll take a look at it; could you send them to me (off-list)?
>
> Here it is. The cpp looks... not so good as I tried to comment out as much as
> possible to keep the info small. But I don't know if you even need it. The file
> dbg.x is the one I load into gdb and makes it crash with the above command,
> I just tested this again.
>
> Thanks for your help.
OK, I can reproduce it. It looks like a bug in the stab reader.
Here's the stab; newlines added for clarity but I don't swear I got
them in the right place.
CMainTask:Tt(0,25)=s148!1,020,(16,31);
__as::(0,26)=##(0,27)=&(0,25);:RC9CMainTask;2A.;
CMainTask::(0,28)=##(0,29)=*(0,25);:RC9CMainTask;2A.
(0,30)=#(0,25),(0,20),(0,29),(0,1),(0,20);:_._9CMainTask;2A*1;(16,31);
(0,31)=##(0,29);:PcUlUl;2A.;
Action::(0,32)=##(0,20);:;2A*2;(16,31);;;~%(16,31);
We're completely botching up the parsing of the constructor. The
problem seems to be the presence of constructor, destructor,
constructor. The bug will be, in current CVS, in stabsread.c around
line 2468 in the has_destructor && has_other case.
It looks like I got the linked list management wrong; I have this
habitual problem with linked lists. The bug may be pretty easy to spot
but I don't have time to dig for it today.
Hope this helps!
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-07 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 9:01 Fabian Cenedese
2004-09-01 9:18 ` Fabian Cenedese
2004-09-02 12:20 ` gdb 6.1.1 (PPC) crash (long) AND gdb crash in cp_print_class_method Dave Korn
2004-09-02 12:59 ` Fabian Cenedese
2004-09-02 14:07 ` Dave Korn
2004-09-02 22:48 ` Craig Jeffree
2004-09-07 14:41 ` Dave Korn
2004-09-02 11:59 ` gdb 6.1.1 (PPC) crash (long) Fabian Cenedese
2004-09-07 14:50 ` Daniel Jacobowitz
[not found] ` <5.2.0.9.1.20040907170934.01d457f8@NT_SERVER>
2004-09-07 17:02 ` Daniel Jacobowitz [this message]
2004-09-29 5:27 ` Craig Jeffree
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=20040907170233.GA8073@nevyn.them.org \
--to=drow@false.org \
--cc=Cenedese@indel.ch \
--cc=gdb@sources.redhat.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