From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16193 invoked by alias); 15 Jan 2002 21:33:10 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16109 invoked from network); 15 Jan 2002 21:33:06 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 15 Jan 2002 21:33:06 -0000 Received: from cse.cygnus.com (cse.sfbay.redhat.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id NAA20200; Tue, 15 Jan 2002 13:33:01 -0800 (PST) Received: (from kev@localhost) by cse.cygnus.com (8.11.6/8.11.6) id g0FLWD202966; Tue, 15 Jan 2002 14:32:13 -0700 Date: Tue, 15 Jan 2002 13:33:00 -0000 From: Kevin Buettner Message-Id: <1020115213213.ZM2965@localhost.localdomain> In-Reply-To: ccroswhite@get2chip.com "Re: GDB and 64 bit" (Jan 15, 12:39pm) References: <3C447EC6.91105808@get2chip.com> <1020115202130.ZM2595@localhost.localdomain> <3C449381.E96E8CC4@get2chip.com> X-Mailer: Z-Mail (4.0.1 13Jan97 Caldera) To: ccroswhite@get2chip.com, Kevin Buettner Subject: Re: GDB and 64 bit Cc: gdb@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-01/txt/msg00170.txt.bz2 On Jan 15, 12:39pm, ccroswhite@get2chip.com wrote: > Here is an instance of both 1 and 2: Thanks. > > gdb bin-sunos5/meta-g [...] > Program received signal SIGABRT, Aborted. > 0xffffffff7e6a3074 in _libc_kill () from /usr/lib/64/libc.so.1 > (gdb) where > #0 0xffffffff7e6a3074 in _libc_kill () from /usr/lib/64/libc.so.1 > #1 0xffffffff7e63cd44 in abort () from /usr/lib/64/libc.so.1 I agree that it does appear that GDB is confused about whether it's debugging 32- or 64-bit code. BTW, the sign extension problem looks familiar. See http://sources.redhat.com/ml/gdb/2001-10/msg00036.html > #2 0x100ae3ab4 in Letext () > #3 0x100a0dbec in fre () > #4 0x100a12ab0 in free () > #5 0x1009f0764 in Tcl_Main () > #6 0x1000e2244 in main () > (gdb) break main.c:1 > Breakpoint 1 at 0xe0e20: file main.c, line 1. > (gdb) run > The program being debugged has been started already. > Start it from the beginning? (y or n) y > Starting program: /home/csun/code2/src/bin-sunos5/meta-g > warning: Cannot insert breakpoint 1: > Cannot access memory at address 0xe0e20 Are you able to successfully run to a breakpoint in main() if you set the breakpoint on the very first run of the program? Sometimes GDB has difficulties setting breakpoints when rerunning the program. (This should be fixed, but I'm trying to determine whether or not you can't run to _any_ breakpoint or if it's just a problem with rerunning the program...) Thanks again, Kevin