Hello,

We are using 2.6.16.46-0.12-default kernel.
And GNU gdb 6.6 version.

We are getting following error while using gdb for core file.

SERVER> gdb $BIN/sia core
GNU gdb 6.6
Copyright (C) 2006 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 "i586-suse-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".

warning: Can't read pathname for load map: Input/output error.

warning: .dynamic section for "/lib/libc.so.6" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/ld-linux.so.2" is not at the expected address (wrong library or version mismatch?)
Reading symbols from /lib/libnss_nis.so.2...done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /usr/lib/libstdc++.so.5...done.
Loaded symbols for /usr/lib/libstdc++.so.5
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Error while mapping shared library sections:
tead of standard output
a filename can be specified using the LD_DEBUG_OUTPUT environment variable.
: No such file or directory.
Core was generated by `sia'.
Program terminated with signal 11, Segmentation fault.
#0 0x08248cc0 in ?? ()
(gdb) q


I am not so familiar with the gdb application so I might be missing something very obvious. Please suggest.


Thanx,
admin

Sort of looks as if all is Good and you should just get on with the job of debugging!

Can I suggest the command
where
as a Good one to start with.

help where
Print backtrace of all stack frames, or innermost COUNT frames.
With a negative argument, print outermost -COUNT frames.
Use of the 'full' qualifier also prints the values of the local variables.

I do wonder from the messages if perhaps the core file or the executable were not perhaps generated on a different system (or version of the system) to the one you are running gdb on.

Also does the executable have debug symbols in it? (ie. compiled with the -g options and hasn't been "strip"ped.