From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8895 invoked by alias); 19 Feb 2007 01:25:17 -0000 Received: (qmail 8875 invoked by uid 22791); 19 Feb 2007 01:25:16 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 19 Feb 2007 01:25:10 +0000 Received: from dsl093-172-095.pit1.dsl.speakeasy.net ([66.93.172.95] helo=caradoc.them.org) by nevyn.them.org with esmtp (Exim 4.63) (envelope-from ) id 1HIxH9-0004MV-SU; Sun, 18 Feb 2007 20:25:07 -0500 Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HIxH9-0002zN-7F; Sun, 18 Feb 2007 20:25:07 -0500 Date: Mon, 19 Feb 2007 09:43:00 -0000 From: Daniel Jacobowitz To: Barry Branham Cc: gdb@sourceware.org Subject: Re: build v6.6 -m32 on x86_64 Message-ID: <20070219012507.GA11408@caradoc.them.org> Mail-Followup-To: Barry Branham , gdb@sourceware.org References: <1171838559.6353.6.camel@emc2.branham.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1171838559.6353.6.camel@emc2.branham.ws> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-02/txt/msg00192.txt.bz2 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