From: bemis <bemis@iol.unh.edu>
To: gdb@sources.redhat.com
Subject: gdb
Date: Wed, 29 May 2002 13:06:00 -0000 [thread overview]
Message-ID: <3CF5357E.67EE2479@iol.unh.edu> (raw)
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
next reply other threads:[~2002-05-29 20:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 13:06 bemis [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 7:05 Gdb Russell Shaw
2006-10-25 12:49 ` Gdb Daniel Jacobowitz
2006-10-25 13:38 ` Gdb Russell Shaw
2006-10-25 14:17 ` Gdb Daniel Jacobowitz
2006-10-25 16:29 ` Gdb Russell Shaw
2006-10-25 20:16 ` Gdb Eli Zaretskii
2006-10-25 20:08 ` Gdb Eli Zaretskii
2006-10-26 2:28 ` Gdb Russell Shaw
2006-10-26 7:11 ` Gdb Eli Zaretskii
2006-10-26 8:16 ` Gdb Russell Shaw
2006-10-26 20:01 ` Gdb Jim Blandy
2006-10-27 3:29 ` Gdb Russell Shaw
2002-07-25 19:33 gdb Richard A. Painter
2002-07-30 20:37 ` gdb Daniel Jacobowitz
2002-03-22 7:18 gdb Kees Everaars
2002-03-26 17:04 ` gdb Michael Snyder
[not found] <20011117045052.5412.qmail@web13905.mail.yahoo.com>
2001-11-07 6:01 ` GDB Christopher Faylor
2001-02-27 9:14 gdb Mathieu Dube
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=3CF5357E.67EE2479@iol.unh.edu \
--to=bemis@iol.unh.edu \
--cc=gdb@sources.redhat.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