From: Mark Kettenis <kettenis@gnu.org>
To: gdb@sources.redhat.com
Cc: jyates@netezza.com, cagney@gnu.org
Subject: Re: Can one debug 32-bit x86 images with an x86_64 gdb?
Date: Tue, 04 Jan 2005 21:18:00 -0000 [thread overview]
Message-ID: <200501042118.j04LIAGP001538@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41DB0457.4010903@gnu.org> (message from Andrew Cagney on Tue, 04 Jan 2005 16:02:15 -0500)
Date: Tue, 04 Jan 2005 16:02:15 -0500
From: Andrew Cagney <cagney@gnu.org>
Since this was vendor specific I replied on the
fedora-tools-list@redhat.com.
http://www.redhat.com/mailman/listinfo/fedora-tools-list
Short summary: the vendor (Red Hat) gcc -m32 is tested and works well
with the vendor debugger; when it comes to a custom compiler many things
could go wrong.
Ah, but I'd like to add that this should work for the official GNU
toolchain too. So if this doesn't work for the latest official
releases or snapshot of GCC or GDB, please submit a detailed bug
report with a self-contained testcase.
Mark
prev parent reply other threads:[~2005-01-04 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 17:46 John Yates
2005-01-04 21:03 ` Andrew Cagney
2005-01-04 21:18 ` Mark Kettenis [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=200501042118.j04LIAGP001538@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jyates@netezza.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