From: Daniel Jacobowitz <drow@false.org>
To: Kalpana Ramamurthy <kal_pana@hotmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 5.3 not debugging properly on Linux kernel 2.6
Date: Thu, 22 Feb 2007 19:57:00 -0000 [thread overview]
Message-ID: <20070222165609.GA12557@caradoc.them.org> (raw)
In-Reply-To: <BAY113-F64ACA4620E28B1AA85E45E88F0@phx.gbl>
Please don't copy both lists with a question.
On Thu, Feb 22, 2007 at 04:50:17PM +0000, Kalpana Ramamurthy wrote:
> Hello,
>
> We are running our native OS on a linux kernel version 2.6 (on a RHEL 4.2
> system). Debugging using
> gdb 5.3 gives a problem "Cannot recognize signal trampoline". As a result,
> we absolutely cannot do any single stepping. Is this a compatibility issue ?
> Should I not be using gdb 5.3 with underlying linux kernel being 2.6 ?
Probably not. I have no idea what patches you might need from more
recent versions of GDB, since you are using a debugger from 2002 with
a kernel from probably 2006. You would have better luck using RHEL's
included GDB, or moving your patches to a more recent release.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-02-22 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 16:56 Kalpana Ramamurthy
2007-02-22 19:57 ` 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=20070222165609.GA12557@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=kal_pana@hotmail.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