From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17092 invoked by alias); 24 Jun 2003 02:00: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 17037 invoked from network); 24 Jun 2003 02:00:30 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 24 Jun 2003 02:00:30 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h5O20VH15792 for ; Mon, 23 Jun 2003 22:00:31 -0400 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 h5O20UI06260; Mon, 23 Jun 2003 22:00:30 -0400 Received: from [150.1.200.14] (vpn50-52.rdu.redhat.com [172.16.50.52]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5O20Td15683; Mon, 23 Jun 2003 22:00:29 -0400 Subject: RE: Building Insight snapshot on CygWin? From: Keith Seitz To: Kevin Powell Cc: "insight@sources.redhat.com" In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1056420563.1574.90.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Tue, 24 Jun 2003 02:00:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q2/txt/msg00186.txt.bz2 On Mon, 2003-06-23 at 18:45, Kevin Powell wrote: > As promised, here is the result of using an unoptimized insight/gdb. BTW, thanks for the tip on turning off the optimizations. At least now I can get a usable (not to me, but maybe to others) backtrace. > > The executive summary is that the unoptimized gdb behaves a bit better than my first attempt. At least now I can set a breakpoint and run to it. However, the first time I try to step, gdb crashes with the same segfault as before. And, to answer your question from the last email, it really is gdb that is crashing -- the target program runs fine both under the distributed gdb and outside of the debugger. And, now I know the reason why it crashes: > This is perfect! Insight isn't even in the backtrace! :-) Please send/forward your excellent message to the gdb list. They've been churning the dwarf2 readers for a little while now, and it looks like you've either uncovered a bug or are missing a recent patch. In either case, the whizzes on the gdb list (gdb at sources dot redhat dot com) will be able to guide you better. Keith PS. Your message is perfect! An example session and a backtrace! How refreshing!