From: Daniel Jacobowitz <dan@debian.org>
To: Wolfgang Wander <wwc@rentec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with gdb back-traces on AMD64 (32 bit executables)
Date: Thu, 16 Jun 2005 16:40:19 -0400 [thread overview]
Message-ID: <20050616204019.GA8434@nevyn.them.org> (raw)
In-Reply-To: <17073.38338.924758.578274@gargle.gargle.HOWL>
On Thu, Jun 16, 2005 at 11:07:46AM -0400, Wolfgang Wander wrote:
> This is regarding a gdb problem regarding stack back-traces with
> AMD64 and -m32 compiled executables. When the program receives
> a signal inside a shared library of an m32 executable (or if
> one attaches to such a program and it executes a shared library
> function) back traces are useless.
>
> I'm sending this to the kernel list for two reasons:
>
> a) the gdb maintainers have not shown any interest in the issue, yet
> ;-), maybe because of b)
> b) the problem only affects 2.6 kernels, 2.4 kernels are fine.
It's not a kernel bug. Please try GDB CVS again, since HJ recently
committed a related fix for x86_64 GDB.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-06-16 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 15:07 problem with gdb back-traces on AMD64 (32 bit executables) Wolfgang Wander
2005-06-16 20:40 ` 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=20050616204019.GA8434@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wwc@rentec.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