Message-ID: <007101bf76c3$a4572ca0$293f8589@gv015029.bgo.nera.no> From: "Gisle Vanem" To: Subject: Re: Help in porting wget Date: Mon, 14 Feb 2000 09:15:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Reply-To: djgpp AT delorie DOT com Doug Kaufman said: >is. Since I am not a programmer, I think I need some help interpreting >the crashback. The symified crashback follow: > >270056/1270056] > >TCP/IP shutdown: Segmentation violation >Exiting due to signal SIGABRT Watt-32 installs signal-handlers for SIGSEGV and others. This handler sends the SIGABRT signal (via raise (SIGABRT)). The reg-dump and trace-back should be (via some tricks) the same as if not trapping SIGSEGV ourself. >Page fault at eip=0004c539, error=0004 >eax=00000008 ebx=00000000 ecx=00000000 edx=00000000 esi=00067f2c edi=00000008 >ebp=000f0558 esp=000f054c program=F:\WGET1\WGET-1.5-3\SRC\WGET.EXE >cs: sel=00e7 base=10310000 limit=0012ffff >ds: sel=00ef base=10310000 limit=0012ffff >es: sel=00ef base=10310000 limit=0012ffff >fs: sel=00ff base=00000000 limit=0010ffff >gs: sel=00ff base=00000000 limit=0010ffff >ss: sel=00ef base=10310000 limit=0012ffff >App stack: [000f06d8..000706d8] Exceptn stack: [000700e0..0006e1a0] > >Call frame traceback EIPs: > 0x0004c539 _free+77 Crashes in free() is most certainly caused by trashing memory allocated by malloc(), calloc() or strdup(). Watch for overwrites of blocks allocated by those functions. > 0x0001721b _freeurl+199, line 349 of url.c > 0x000168cc _retrieve_url+896, line 420 of retr.c > 0x00015184 _recursive_retrieve+2196, line 411 of recur.c > 0x00012eb4 _main+3360, line 700 of main.c > 0x0004951e ___crt1_startup+178 This is just the call-sequence in reverse. Probably main() called recursive_retrieve() which called retrieve_url() etc. Gisle V.