From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15334 invoked by alias); 21 Jan 2005 23:32:32 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 15283 invoked from network); 21 Jan 2005 23:32:27 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 21 Jan 2005 23:32:27 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j0LNWRCk013856 for ; Fri, 21 Jan 2005 18:32:27 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j0LNWRO28016; Fri, 21 Jan 2005 18:32:27 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j0LNWQEU012394; Fri, 21 Jan 2005 18:32:27 -0500 Subject: Re: SEG FAULT From: Keith Seitz To: Thomas Fusco Cc: "insight@sources.redhat.com" In-Reply-To: <41F16D23.3060409@link.com> References: <41F16D23.3060409@link.com> Content-Type: text/plain Message-Id: <1106350346.3653.75.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Fri, 21 Jan 2005 23:32:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q1/txt/msg00026.txt.bz2 On Fri, 2005-01-21 at 12:59, Thomas Fusco wrote: > I'm getting a "SEGMENTATION FAULT" with the address and I'm having > trouble getting to the address using insight. I can locate an address > if I'm in the function browser and I disassemble and hunt for the > address (using window). But what if I do not know which function I'm > getting the SEGMENTATION FAULT on. It's tedious to hunt through all the > code. I'm afraid you're going to have to give a little more information. Can you see a stack backtrace? [Open stack window; or open console window and type "bt".] You should be able to deduce what happened unless the program did something that corrupted the stack or whatnot. If you send the output of "bt", I can tell you the best way to proceed. [Feel free to obfuscate function names if you're worried about it.] If you know the address where the segfault occurred, you can open a console window and type "info symbol ADDRESS" to find out what symbol best matches the address: $ ./gdb -nw -nx -q gdb (gdb) p main $1 = {int (int, char **)} 0x8090e70
(gdb) info symbol 0x8090e74 main + 4 in section .text Keith