On Tue, Mar 08, 2005 at 02:43:07AM +0100, christophe wrote: > [EMAIL PROTECTED]:~/nmap-3.81$ gdb nmap > GNU gdb 6.3-debian > [blablabla] > > (gdb) r -oS - 192.168.0.1 > Starting program: /home/christophe/nmap-3.81/nmap -oS - 192.168.0.1 > > Program received signal SIGSEGV, Segmentation fault. > 0x0fd8481c in strlen () from /lib/libc.so.6 > (gdb) bt > #0 0x0fd8481c in strlen () from /lib/libc.so.6 > #1 0x0fd5363c in vfprintf () from /lib/libc.so.6 > #2 0x0fd73d68 in vsnprintf () from /lib/libc.so.6 > #3 0x1001a944 in log_write (logt=1, fmt=0x100513e4 "\nStarting %s %s ( > %s ) at %s\n") at output.cc:537 > #4 0x10005bfc in nmap_main (argc=4, argv=0x7ffff554) at nmap.cc:790
Hmm ... that is curious. I wonder if the 4096-byte stack buffer is too large for your system. Could you try changing: char b[4096] to char b[1024] on line 520 of output.cc, recompile, and let us know if it still crashes? If it DOES still crash, what would be useful to see is log of: gdb nmap break log_write r -oS - 192.168.0.1 [ when it stops execution, press 'n', then just keep pressing enter until it crashes, which should be less than twenty keypresses ] If you could send me the output from that test, it would be quite useful. Thanks, Fyodor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
