From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18489 invoked by alias); 19 Nov 2001 21:28:05 -0000 Mailing-List: contact insight-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 18434 invoked from network); 19 Nov 2001 21:28:01 -0000 X-Authentication-Warning: makita.cygnus.com: keiths owned process doing -bs Date: Wed, 03 Oct 2001 14:03:00 -0000 From: Keith Seitz To: Grant Edwards cc: Subject: Re: No step button using insight w/ remote target. In-Reply-To: <20011119152352.A27096@visi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-q4/txt/msg00039.txt.bz2 On Mon, 19 Nov 2001, Grant Edwards wrote: > Maybe... > > I tried setting a watchpoint after it was initialized by > remote_open_1, but execution is so slow, I don't know if the > serial protocol is going to work. It doesn't look like it, but > I'm going to give it a while longer. Let me guess: you're not using an x86 with hardware watchpoints? > If you've got some suggestions for likely suspects, I could set > some breakpoints instead of using a watchpoint. Well, you could grep fro places where inferior_ptid is set and break at those... $ grep -n "inferior_ptid =" *.c | awk -F: '{printf "break %s:%d\n", $1, $2}' > breaks Then source this file into gdb... Ok, this sucks, but I don't know what else to do right now. Keith From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Seitz To: Grant Edwards Cc: Subject: Re: No step button using insight w/ remote target. Date: Mon, 19 Nov 2001 13:28:00 -0000 Message-ID: References: <20011119152352.A27096@visi.com> X-SW-Source: 2001-q4/msg00340.html Message-ID: <20011119132800.w7cNnQ9CiwfCFxoNQ1k4wock81gPpEbVvSsvyDpQYnE@z> On Mon, 19 Nov 2001, Grant Edwards wrote: > Maybe... > > I tried setting a watchpoint after it was initialized by > remote_open_1, but execution is so slow, I don't know if the > serial protocol is going to work. It doesn't look like it, but > I'm going to give it a while longer. Let me guess: you're not using an x86 with hardware watchpoints? > If you've got some suggestions for likely suspects, I could set > some breakpoints instead of using a watchpoint. Well, you could grep fro places where inferior_ptid is set and break at those... $ grep -n "inferior_ptid =" *.c | awk -F: '{printf "break %s:%d\n", $1, $2}' > breaks Then source this file into gdb... Ok, this sucks, but I don't know what else to do right now. Keith