From owner-freebsd-current Sun Oct 20 06:49:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA19931 for current-outgoing; Sun, 20 Oct 1996 06:49:31 -0700 (PDT) Received: from scrooge.ee.swin.oz.au (scrooge.ee.swin.oz.au [136.186.4.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA19918 for ; Sun, 20 Oct 1996 06:49:27 -0700 (PDT) Received: (from dtc@localhost) by scrooge.ee.swin.oz.au (8.6.9/8.6.9) id XAA16448; Sun, 20 Oct 1996 23:49:11 +1000 From: Douglas Thomas Crosher Message-Id: <199610201349.XAA16448@scrooge.ee.swin.oz.au> Subject: Re: kern/1848: breakpoints in shared libraries don't fire To: grog@lemis.de Date: Sun, 20 Oct 1996 23:49:10 +1000 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199610201240.OAA12535@freebie.lemis.de> from "Greg Lehey" at Oct 20, 96 02:40:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It's possible to set breakpoints in shared libraries, but > executing the code doesn't cause a SIGTRACE. I've also noticed this for breakpoints placed in pages mapped in from a file (a lisp core file). Regards Douglas Crosher