From owner-freebsd-questions Wed Jan 20 06:47:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07036 for freebsd-questions-outgoing; Wed, 20 Jan 1999 06:47:28 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from jau.tmt.tele.fi (jau.tmt.tele.fi [194.252.70.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07031 for ; Wed, 20 Jan 1999 06:47:26 -0800 (PST) (envelope-from jau@jau.tmt.tele.fi) Received: (from jau@localhost) by jau.tmt.tele.fi (8.9.1/8.9.1/JAU-2.2) id QAA00683 for questions@freebsd.org; Wed, 20 Jan 1999 16:47:16 +0200 (EET) From: "Jukka A. Ukkonen" Message-Id: <199901201447.QAA00683@jau.tmt.tele.fi> Subject: Odd netscape-communicator-4.5 crash when clicking mailto-anchors To: questions@FreeBSD.ORG Date: Wed, 20 Jan 1999 16:47:15 +0200 (EET) Latin-Date: Miercuri XX Ianuarie a.d. MCMXCIX Organization: Internet Services R&D / Sonera Ltd. Finland Phone: +358-2040-4025 (office) / +358-400-606671 (mobile) Content-Conversion: prohibited X-Mailer: ELM [version 2.4 PL25+pgp] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy! Has anyone else seen this happen with communicator-4.5 when clicking mailto-anchors? 400 communicator-4.5 PSIG SIGALRM caught handler=0x9067b0 mask=0x0 code=0x0 400 communicator-4.5 CALL gettimeofday(0xefbfbb4c,0) 400 communicator-4.5 RET gettimeofday 0 400 communicator-4.5 CALL sigreturn(0xefbfbbe8) 400 communicator-4.5 RET sigreturn JUSTRETURN 400 communicator-4.5 PSIG SIGALRM caught handler=0x9067b0 mask=0x0 code=0x0 400 communicator-4.5 CALL gettimeofday(0xefbfbacc,0) 400 communicator-4.5 RET gettimeofday 0 400 communicator-4.5 CALL sigreturn(0xefbfbb68) 400 communicator-4.5 RET sigreturn JUSTRETURN 400 communicator-4.5 PSIG SIGSEGV caught handler=0x908620 mask=0x0 code=0xc 400 communicator-4.5 CALL getpid 400 communicator-4.5 RET getpid 400/0x190 400 communicator-4.5 CALL kill(0x190,0xa) 400 communicator-4.5 PSIG SIGBUS SIG_DFL 400 communicator-4.5 NAMI "communicator-4.5.core" First it gets a segmentation violation, tries to recover from that one, and immediately (and rightfully) gets also a bus error. In general it is rather hard to recover from SIGSEGV, because there is nothing much else to do, but a stack unwind, which may fail, because the stack frames are already messed up. So, the second SIGBUS is to be expected, but why does it generate the SIGSEGV? Oops, I almost forgot this, but the binary is the one available among 2.2.8 packages at ftp.freebsd.org. I did not compile it locally myself. Any tips and ideas would be welcome. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Internet Services R&D / Sonera Ltd. /__ M.Sc. (sw-eng & cs) (Phone) +358-2040-4025 / Internet: Jukka.Ukkonen@sonera.fi (Fax) +358-2040-64724 / Internet: jau@iki.fi (Mobile) +358-400-606671 v Internet: ukkonen@nic.funet.fi (Home&Fax) +358-9-6215280 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message