From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26580 invoked by alias); 12 Apr 2002 09:13:38 -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 26573 invoked from network); 12 Apr 2002 09:13:33 -0000 Received: from unknown (HELO mirapoint.inter.net.il) (192.114.186.20) by sources.redhat.com with SMTP; 12 Apr 2002 09:13:33 -0000 Received: from zaretsky (diup-217-177.inter.net.il [213.8.217.177]) by mirapoint.inter.net.il (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id AAZ14089; Fri, 12 Apr 2002 12:13:19 +0300 (IDT) Date: Fri, 12 Apr 2002 02:13:00 -0000 From: "Eli Zaretskii" To: mludvig@suse.cz Message-Id: <9743-Fri12Apr2002120839+0300-eliz@is.elta.co.il> CC: gdb@sources.redhat.com In-reply-to: <3CB5B5F1.7010809@suse.cz> (message from Michal Ludvig on Thu, 11 Apr 2002 18:12:33 +0200) Subject: Re: Strange segfaults of gdb Reply-to: Eli Zaretskii References: <3CB5B5F1.7010809@suse.cz> X-SW-Source: 2002-04/txt/msg00203.txt.bz2 > Date: Thu, 11 Apr 2002 18:12:33 +0200 > From: Michal Ludvig > > Breakpoint 1, main () at xmmtest.c:10 > 10 printf("v1=%f, v2=%f, v3=%e\n", v1, v2, v3); > (gdb) p 1 > $1 = 1 > (gdb) c > Continuing. > Segmentation fault (core dumped) > > It doesn't matter which program I run, what I want to print and if I > then want invoke 'run', 'continue' or even 'si'. It segfaults. Core file > doesn't give any reasonable informations. You mean, you cannot even tell from the core file where (inside what function) GDB crashes? That'd be very strange indeed--what could prevent you from getting att his information? Is the core file corrupt or something? What if you run GDB under another GDB--can you see where does the subordinate GDB crash then? > Does anybody have an idea how print, set and step can be related? It's very hard to tell without knowing where's the crash happening.