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 14:50:00 -0000 [thread overview]
Message-ID: <20040907145026.GA4739@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20040902133756.01d474f8@NT_SERVER>
On Thu, Sep 02, 2004 at 01:58:31PM +0200, Fabian Cenedese wrote:
>
> >Hi
> >
> >I get a crash when trying to lookup a symbol with my cross compiled gdb. It's
> >just this one symbol (so far), others I can lookup with no problems.
> >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)?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-07 14:50 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 [this message]
[not found] ` <5.2.0.9.1.20040907170934.01d457f8@NT_SERVER>
2004-09-07 17:02 ` Daniel Jacobowitz
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=20040907145026.GA4739@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