From owner-freebsd-hackers Thu Mar 1 9:46:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id BDE8A37B719 for ; Thu, 1 Mar 2001 09:46:28 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f21Hjts33386 for hackers@freebsd.org; Thu, 1 Mar 2001 12:45:55 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200103011745.f21Hjts33386@hda.hda.com> Subject: Stupid debugging pthread question To: hackers@freebsd.org Date: Thu, 1 Mar 2001 12:44:39 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a stupid question, basically it's how to debug something. I have four cooperating p-threaded processes. One of them keeps getting a SIGSEGV with the address 0x752f422f. I'm not sure if that address is always the same, but with a given compile it is. The thing that's a pain is it is random. The four processes can run for a long time, or through several tests to completion, and then the nasty process gets that SIGSEGV. The thread that receives the SIGSEGV is random, the stack of the SEGV'd thread is trash, the rest of the threads in the offending process still have intact stacks. Arg! Because this is intermittent my temptation is to ignore it and proceed and eventually something will happen to let me figure it out. But it's been going on for a while, and it just happened twice in a row so... Anybody seen anything remotely similar and have a suggestion? How does one dump the stack brute force on an x86? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message