Hi,
attached is the recording of "2>&1 gdb ssh | tee gdb_ssh".
I noticed that all programs I saw segfaulting in the early stages
are "MSB shared objects" but not all shared objects segfault.
So that might be a library problem.
I'll investigate further
Thanks
Siggy
--
bsb-at-psycho-dot-informationsanarchistik-dot-de
or: bsb-at-psycho-dot-i21k-dot-de
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips-linux-gnu"...
(no debugging symbols found)
(gdb) run nfs.winnegan.fake
Starting program: /usr/bin/ssh nfs.winnegan.fake
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
0x2aab566c in ?? () from /lib/ld.so.1
(gdb) where
#0 0x2aab566c in ?? () from /lib/ld.so.1
warning: GDB can't find the start of the function at 0x2aab566c.
GDB is unable to find the start of the function at 0x2aab566c
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x2aab566c for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#1 0x2aab566c in ?? () from /lib/ld.so.1
warning: GDB can't find the start of the function at 0x2aab566b.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) q
Attachment:
signature.asc
Description: Digital signature