From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15384 invoked by alias); 25 Feb 2003 20:51:57 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15363 invoked from network); 25 Feb 2003 20:51:57 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 25 Feb 2003 20:51:57 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id PAA19395 for ; Tue, 25 Feb 2003 15:39:45 -0500 Received: from dash ([192.168.20.34]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id PAA23351 for ; Tue, 25 Feb 2003 15:51:55 -0500 Message-ID: <00e001c2dd10$3d4284e0$2a00a8c0@dash> From: "Kris Warkentin" To: Subject: deferred breakpoints Date: Tue, 25 Feb 2003 20:51:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-02/txt/msg00541.txt.bz2 How difficult do you think deferred breakpoints would be to implement? We have a customer who does a lot of work with shared objects and they'd like to be able to set breakpoints in them and have them persist across runs. I'm thinking that creating a list of breakpoints that could be run through every time a shared object was loaded would do the trick. Can anyone point out any obvious gotcha's? Kris