From: "John Yates" <jyates@netezza.com>
To: "gdb \(E-mail\)" <gdb@sources.redhat.com>
Subject: Can one debug 32-bit x86 images with an x86_64 gdb?
Date: Tue, 04 Jan 2005 17:46:00 -0000 [thread overview]
Message-ID: <F0CD2E5262214F44959AD6AF34ADA66E01D12F7C@mail2.netezza.com> (raw)
We are starting to port our 32 bit product to an x86_64
platform (RH 4.0 beta2). Once we have it running as a
32 bit image (still compiled with gcc 2.96) we will start
the slog to gcc 3.x and a full 64 bit port.
Except for the 32 bit gcc which we have had to migrated
-- our code currently includes numerous anachronisms no
longer accepted by the 3.x compilers -- we have been able
to coax the native system tools (bison, ar, ld, etc) into
compliance with our 32 bit build procedure.
Debugging is a different story. The install gdb image
describes itself as:
6.1post-1.20040607.46rh
x86_64-redhat-linux-gnu
It does not decline to debug our 32 bit images yet it
produces total garbage. Is there a flag or environment
variable that I may have overlooked? Or is a single gdb
image not intended to fulfill both roles?
/john
--
John S. Yates, Jr. 508 665-6897 (voice)
Netezza Inc 508 665-6811 (fax)
200 Crossing Blvd. Framingham, MA 01701
next reply other threads:[~2005-01-04 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 17:46 John Yates [this message]
2005-01-04 21:03 ` Andrew Cagney
2005-01-04 21:18 ` Mark Kettenis
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=F0CD2E5262214F44959AD6AF34ADA66E01D12F7C@mail2.netezza.com \
--to=jyates@netezza.com \
--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