From: Daniel Jacobowitz <dan@debian.org>
To: Ricardo Mendoza <ricmm@kanux.com>
Cc: linux-mips@linux-mips.org
Subject: Re: O2 KGDB problem
Date: Wed, 10 Oct 2007 08:55:53 -0400 [thread overview]
Message-ID: <20071010125553.GA18207@caradoc.them.org> (raw)
In-Reply-To: <470C8F8E.3010301@kanux.com>
On Wed, Oct 10, 2007 at 04:38:38AM -0400, Ricardo Mendoza wrote:
> Been messing around with the O2 and KGDB and well, theres a problem that
> I don't quite know how to tackle, when building a 64-bit kernel with
> mips64 target toolchain and with CONFIG_BUILD_ELF64 and then trying to
> start remote gdb with that image I get a Segfault from gdb. What do you
> think is the cause of this?
>
> I guess its just file format mixup confusing gdb? any pointer from a gdb
> guru
> towards making this work?
I believe a CVS snapshot of GDB will "work" but refuse to show you
line numbers, and if you use a CVS snapshot of gas too then things
will work OK. gas was doing something horribly wrong to the
.debug_line sections it generated.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-10 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 8:38 O2 KGDB problem Ricardo Mendoza
2007-10-10 12:55 ` Daniel Jacobowitz [this message]
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=20071010125553.GA18207@caradoc.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ricmm@kanux.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