From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-9068-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 24861 invoked by alias); 29 May 2002 20:06:25 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 24834 invoked from network); 29 May 2002 20:06:21 -0000
Received: from unknown (HELO iol.unh.edu) (132.177.123.82)
  by sources.redhat.com with SMTP; 29 May 2002 20:06:21 -0000
Received: from iol.unh.edu (astro.iol.unh.edu [132.177.124.6])
	by iol.unh.edu (8.12.3/8.12.3) with ESMTP id g4TK6Ke5009313
	for <gdb@sources.redhat.com>; Wed, 29 May 2002 16:06:20 -0400
Message-ID: <3CF5357E.67EE2479@iol.unh.edu>
Date: Wed, 29 May 2002 13:06:00 -0000
From: bemis <bemis@iol.unh.edu>
Organization: University of New Hampshire
X-Accept-Language: en
MIME-Version: 1.0
To: gdb@sources.redhat.com
Subject: gdb
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-05/txt/msg00323.txt.bz2

Hello,

I am new to using gdb, but I didn't see a really good way to run my
executable inside of gdb.

I am trying to figure out why I am getting a core dump when I am
checking a library in libc.
I have two environment variables:

GCONV_PATH=/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/

iconvdata

LC_ALL=C

then I run my library with the following command:

/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/na
tive/libc/elf/ld-linux.so.2 --library-path
/mnt/u2/bemis/dev/tools/build/alpha7/
bootstrap-gcc_3.0.4/native/libc:/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-g

cc_3.0.4/native/libc/math:/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0

.4/native/libc/elf:/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/nati

ve/libc/dlfcn:/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/li

bc/nss:/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/nis:

/mnt/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/rt:/mnt/u2/

bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/resolv:/mnt/u2/bemi

s/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/crypt:/mnt/u2/bemis/dev

/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/linuxthreads

and then finally I run :
 /mnt/u2/bemis/d
ev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/dlfcn/tstcxaatexit
> /mnt
/u2/bemis/dev/tools/build/alpha7/bootstrap-gcc_3.0.4/native/libc/dlfcn/tstcxaate

xit.out

Really this is all on one command line!  What would be the proper way to
start debugging this with gdb and the core file I get from this when
I run it outside of gdb?
Thanks!
Matt Bemis
University of New Hampshire
Alpha Linux Group