Re: List command question

[Andrew Cagney <cagney at gnu dot org>]

> > > > >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.

As others pointed out, the above is correct.  It found debug information 
for ``entry-point'' and then tried to use it.  Only to barf because the 
the corresponding source files were not installed.  There's not much GDB 
can do when a user's program contains debug info but is missing the 
corresponding source.

What happens if you enter:

	(gdb) list main

Andrew