From owner-freebsd-current Sun Oct 20 07:33:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA22279 for current-outgoing; Sun, 20 Oct 1996 07:33:07 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA22268 for ; Sun, 20 Oct 1996 07:33:03 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id AAA01800; Mon, 21 Oct 1996 00:02:49 +0930 From: Michael Smith Message-Id: <199610201432.AAA01800@genesis.atrad.adelaide.edu.au> Subject: Re: kern/1848: breakpoints in shared libraries don't fire To: dtc@scrooge.ee.swin.oz.au (Douglas Thomas Crosher) Date: Mon, 21 Oct 1996 00:02:49 +0930 (CST) Cc: grog@lemis.de, freebsd-current@freebsd.org In-Reply-To: <199610201349.XAA16448@scrooge.ee.swin.oz.au> from "Douglas Thomas Crosher" at Oct 20, 96 11:49:10 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Douglas Thomas Crosher stands accused of saying: > > > It's possible to set breakpoints in shared libraries, but > > executing the code doesn't cause a SIGTRACE. Setting a breakpoint in a shared library would be Bad, as you don't have any way of telling who else it is shared with. I suspect that the attempt to set the trace is silently failing. > Douglas Crosher -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) [[ ]] realtime instrument control (ph/fax) +61-8-8267-3493 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[