On Tuesday 22 March 2005 9:46 am, Carlo Luciano Bianco wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x77c16137 in strdup () from C:\WINDOWS\system32\msvcrt.dll
To find out what caused that fault, use the bt command: backtrace. It happened in strdup() so that's usually because the string you are trying to copy (or copy to) is not accessible - maybe not properly initialised. The fault is not necessarily in the file identified above, it just showed up there. Use up and down commands after getting the backtrace to inspect the calls that lead to the segmentation fault. > (gdb) continue > Continuing. You can't usually continue after a segmentation fault - or if you try you won't get predictable behaviour. > Should I try something else? bt -- Neil Williams ============= http://www.dcglug.org.uk/ http://www.nosoftwarepatents.com/ http://sourceforge.net/projects/isbnsearch/ http://www.neil.williamsleesmill.me.uk/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3
pgpUP8qKwjLhO.pgp
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
