From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28791 invoked by alias); 3 Nov 2004 18:09:05 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28778 invoked from network); 3 Nov 2004 18:09:04 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 3 Nov 2004 18:09:04 -0000 Received: from zaretski ([80.230.149.157]) by legolas.inter.net.il (MOS 3.5.3-GR) with ESMTP id DAG32042 (AUTH halo1); Wed, 3 Nov 2004 20:09:00 +0200 (IST) Date: Wed, 03 Nov 2004 18:09:00 -0000 From: "Eli Zaretskii" To: David Lecomber Message-ID: <01c4c1cf$Blat.v2.2.2$9add4540@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: "gdb-patches@sources.redhat.com" <1099483707.7521.27.camel@delmo.priv.wark.uk.streamline-computing.com> (message from David Lecomber on Wed, 03 Nov 2004 12:08:27 +0000) Subject: Re: [PATCH] Seg fault whilst stepping when watch set [ping!] [in breakpoint.c] Reply-to: Eli Zaretskii References: <1097972182.22738.7.camel@localhost.localdomain> <1098720391.1935.0.camel@delmo.priv.wark.uk.streamline-computing.com> <1099347096.31287.3.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com> <01c4c095$Blat.v2.2.2$3f440920@zahav.net.il> <1099385491.31287.19.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com> <01c4c123$Blat.v2.2.2$ffbe6360@zahav.net.il> <1099483707.7521.27.camel@delmo.priv.wark.uk.streamline-computing.com> X-SW-Source: 2004-11/txt/msg00047.txt.bz2 > From: David Lecomber > Date: Wed, 03 Nov 2004 12:08:27 +0000 > > Curiously on Fedora 2 I get a seg fault, and > > Error in re-setting breakpoint 2: > No symbol "i" in current context. > > But on Redhat 9, I get no segfault but do see the above error repeated 3 > times.. Hmm... Fedora? Could that be a side-effect of the exec-shield feature? Since I don't have access to a Fedora machine, I cannot debug this myself. I will try to figure out what happens using your session transcript. Stay tuned.