From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27689 invoked by alias); 2 Nov 2004 21:40:35 -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 27681 invoked from network); 2 Nov 2004 21:40:34 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 2 Nov 2004 21:40:34 -0000 Received: from zaretski ([80.230.144.19]) by legolas.inter.net.il (MOS 3.5.3-GR) with ESMTP id CZZ79034 (AUTH halo1); Tue, 2 Nov 2004 23:40:31 +0200 (IST) Date: Tue, 02 Nov 2004 21:40:00 -0000 From: "Eli Zaretskii" To: David Lecomber Message-ID: <01c4c123$Blat.v2.2.2$ffbe6360@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb-patches@sources.redhat.com In-reply-to: <1099385491.31287.19.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com> (message from David Lecomber on Tue, 02 Nov 2004 08:54:00 +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> X-SW-Source: 2004-11/txt/msg00037.txt.bz2 [Please keep the discussion on the mailing list.] > From: David Lecomber > Date: Tue, 02 Nov 2004 08:54:00 +0000 > > > Can you post a short test program, preferably in C, that can be used > > to reproduce this problem? I don't think I've ever seen such crashes. > > If only I could! The only example I can make it happen with is using > the Intel Fortran Compiler for a piece of F90. Then please post an annotated debug session (debugging GDB with itself, where the inferior GDB has the F90 compiled program as its debuggee) which shows the problem and explains how you arrived at the conclusion that the patch you suggested is the correct one. I need to understand the details of these crashes to be able to consider the validity of the patch. > I can supply you with the binary if you'd like to have a go, but I > don't see any other way we'll be able to produce this. If the binary is short, then you could alternatively mail it to me as a binary attachment together with the source and instructions how to reproduce the crash.