From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 785 invoked by alias); 5 Jul 2011 07:24:42 -0000 Received: (qmail 773 invoked by uid 22791); 5 Jul 2011 07:24:41 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from nm21-vm0.bullet.mail.sp2.yahoo.com (HELO nm21-vm0.bullet.mail.sp2.yahoo.com) (98.139.91.220) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 05 Jul 2011 07:24:23 +0000 Received: from [98.139.91.64] by nm21.bullet.mail.sp2.yahoo.com with NNFMP; 05 Jul 2011 07:24:22 -0000 Received: from [98.139.91.5] by tm4.bullet.mail.sp2.yahoo.com with NNFMP; 05 Jul 2011 07:24:22 -0000 Received: from [127.0.0.1] by omp1005.mail.sp2.yahoo.com with NNFMP; 05 Jul 2011 07:24:22 -0000 Received: (qmail 18849 invoked by uid 60001); 5 Jul 2011 07:24:22 -0000 Received: from [2.176.234.233] by web111713.mail.gq1.yahoo.com via HTTP; Tue, 05 Jul 2011 00:24:21 PDT References: <1309847935.50900.YahooMailNeo@web111702.mail.gq1.yahoo.com> Message-ID: <1309850661.18621.YahooMailNeo@web111713.mail.gq1.yahoo.com> Date: Tue, 05 Jul 2011 07:24:00 -0000 From: Mahmood Naderan Reply-To: Mahmood Naderan Subject: Re: GDB doesnot catches segmentation fault To: "pmuldoon@redhat.com" Cc: "gdb@sourceware.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-07/txt/msg00014.txt.bz2 >Then: >gdb gdb --core=3Dyourcore.pid >Where "youcore.pid" is the core-file that GDB generated on crash Where does it save that file? I can not find it // Naderan *Mahmood; ----- Original Message ----- From: Phil Muldoon To: Mahmood Naderan Cc: "gdb@sourceware.org" Sent: Tuesday, July 5, 2011 11:43 AM Subject: Re: GDB doesnot catches segmentation fault Mahmood Naderan writes: > Hi > I have attached a PID to gdb. Although the code crashed with segmentation= fault, but gdb ignores that and I am not able to view backtrace. > 0x0000000000447bfb in Event::initialized (this=3D0x41ec648) at build/ALPH= A_FS/sim/eventq.hh:84 > 84=A0=A0=A0=A0=A0=A0=A0=A0=A0 initialized() const > (gdb) c > Continuing. > Segmentation fault > mahmood@mpc:~$ This looks like GDB crashed with a segmentation fault. There is not enough information to work with here.=A0 There are two things you could try: A newer GDB, the problem might already have been fixed. Or, submit a backtrace for GDB. If you have debug information installed for GDB you can do this.=A0 I am not sure of the method for installing debug information for installed packages with Ubuntu.=A0 But assuming you do have them: Type:=20 ulimit -c unlimited in the terminal where you will launch GDB=A0 (This will allow core-files to be generated). Attach GDB to the program (as you did above) and replicate the scenario to crash GDB. Then: gdb gdb --core=3Dyourcore.pid Where "youcore.pid" is the core-file that GDB generated on crash. Then type "bt" into GDB.=A0 This will produce a backtrace of the crashing GDB process. Then create a bug at:=20 http://sourceware.org/bugzilla/=20 for gdb, and paste the "bt" output.=A0 Also include any supplemental information you think is useful. Cheers, Phil