From: Daniel Jacobowitz <drow@false.org>
To: Barry Branham <bhb@branham.ws>
Cc: gdb@sourceware.org
Subject: Re: build v6.6 -m32 on x86_64
Date: Mon, 19 Feb 2007 09:43:00 -0000 [thread overview]
Message-ID: <20070219012507.GA11408@caradoc.them.org> (raw)
In-Reply-To: <1171838559.6353.6.camel@emc2.branham.ws>
On Sun, Feb 18, 2007 at 04:42:39PM -0600, Barry Branham wrote:
> Hello,
>
> Are there ./configure options which will result in building a 32 bit
> version of gdb. I'm currently running FC6 64 on an AMD Athon 64 X2
> system.
>
> I have the FC6 32bit 6.5 rpm installed but am getting an
> "thread_get_info_callback: cannot get thread info: generic error"
> when trying to debug programs linked with libpthread.so.
>
> So thought I'd try 6.6.
You just need to set CC or CFLAGS appropriately before running
configure. However, I know of at least one kernel bug in the x86_64
ptrace emulation for 32-bit processes, so I really don't recommend
doing this if you can avoid it - I would expect trouble with thread
debugging as a symptom of that.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-02-19 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 9:33 Barry Branham
2007-02-19 9:43 ` 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=20070219012507.GA11408@caradoc.them.org \
--to=drow@false.org \
--cc=bhb@branham.ws \
--cc=gdb@sourceware.org \
/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