From: Manoj Iyer <manjo@austin.ibm.com>
To: Monika Chaddha <monika@acmet.com>
Cc: gdb@sources.redhat.com
Subject: RE: List command question
Date: Mon, 17 May 2004 15:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0405171010430.16025@lazy> (raw)
In-Reply-To: <004801c43a43$36fc9800$5100a8c0@monika>
> >manjo@nefertiti:~/projects/src> cc -o ~/tests/test ~/tests/test.c
> >manjo@nefertiti:~/projects/src> ./gdb/gdb ~/tests/test
> >GNU gdb 2004-04-17-cvs
> >Copyright 2004 Free Software Foundation, Inc.
> >GDB is free software, covered by the GNU General Public License, and
> you
> >are
> >welcome to change it and/or distribute copies of it under certain
> >conditions.
> >Type "show copying" to see the conditions.
> >There is absolutely no warranty for GDB. Type "show warranty" for
> >details.
> >This GDB was configured as "powerpc64-gnu-linux"...Using host
> libthread_db
> >libra
> >ry "/lib64/tls/libthread_db.so.1".
> >
> >(gdb) list
> >1 ../sysdeps/powerpc/powerpc32/elf/start.S: No such file or
> >directory.
> > in ../sysdeps/powerpc/powerpc32/elf/start.S
> >(gdb) quit
> >
> >
IMHO this output is simply misleading, it should print something
meaningful, like no symbols found, or no debug info in executable, or
compile with -g to generate more debug info etc.... 'file not found' is
not a clear indicator of what is going on.
--
Manoj Iyer
next prev parent reply other threads:[~2004-05-17 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 18:29 Manoj Iyer
2004-05-14 19:27 ` Andreas Schwab
2004-05-15 8:37 ` Eli Zaretskii
2004-05-15 13:16 ` Andreas Schwab
2004-05-15 18:07 ` Ramana Radhakrishnan
2004-05-15 7:40 ` Monika Chaddha
2004-05-17 15:29 ` Manoj Iyer [this message]
2004-05-17 18:35 ` Andrew Cagney
2004-05-19 2:24 ` Manoj Iyer
2004-05-19 14:22 ` Andrew Cagney
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=Pine.LNX.4.58.0405171010430.16025@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb@sources.redhat.com \
--cc=monika@acmet.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