From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23939 invoked by alias); 1 Jun 2004 17:41:57 -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 23889 invoked from network); 1 Jun 2004 17:41:56 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 1 Jun 2004 17:41:56 -0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i51Hfti5028428 for ; Tue, 1 Jun 2004 13:41:55 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i51Hfsw03173; Tue, 1 Jun 2004 13:41:54 -0400 Received: from redhat.com (dhcp-172-16-25-160.sfbay.redhat.com [172.16.25.160]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id i51HfrP01705; Tue, 1 Jun 2004 10:41:53 -0700 Message-ID: <40BCBFE1.6010103@redhat.com> Date: Tue, 01 Jun 2004 17:41:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.4.2) Gecko/20040301 MIME-Version: 1.0 To: Elena Zannoni CC: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: [HEADS-UP] gdb segfault References: <409C5170.8040702@redhat.com> <40A0272D.5080702@gnu.org> <16572.43064.43519.774441@localhost.redhat.com> In-Reply-To: <16572.43064.43519.774441@localhost.redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00016.txt.bz2 Elena Zannoni wrote: > Andrew Cagney writes: > > > Hey yo -- > > > > > > gdb is seg-faulting immediately whenever its run with --noasync. > > > I have an old build from the beginning of March that doesn't > > > do it (nor do even older ones), so it's probably a change > > > from between then and now. > > > > > > It crashes in display_gdb_prompt, as called from > > > tui_command_loop. Here's a backtrace. > > > > Sounds like it's time to delete --noasync .... > > I think so, yes. It bothers me that ^C doesn't work with async, and I can't fall back to noasync to make it work. I think async should work (wrt. ^C, at least), before we delete noasync.