From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25797 invoked by alias); 31 Dec 2009 06:27:57 -0000 Received: (qmail 25788 invoked by uid 22791); 31 Dec 2009 06:27:57 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from lo.gmane.org (HELO lo.gmane.org) (80.91.229.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 31 Dec 2009 06:27:53 +0000 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NQEVh-0007ET-I0 for gdb@sources.redhat.com; Thu, 31 Dec 2009 07:27:49 +0100 Received: from h86-62-88-129.ln.rinet.ru ([86.62.88.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 Dec 2009 07:27:49 +0100 Received: from vladimir by h86-62-88-129.ln.rinet.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 Dec 2009 07:27:49 +0100 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: [Bug:cli] Loading user-defined function generates an internal error Followup-To: gmane.comp.gdb.devel Date: Thu, 31 Dec 2009 06:27:00 -0000 Message-ID: References: <19258.59036.731093.439412@totara.tehura.co.nz> <20091230054617.GA548@adacore.com> <19259.5113.884675.579179@totara.tehura.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit User-Agent: KNode/4.3.2 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: 2009-12/txt/msg00179.txt.bz2 Nick Roberts wrote: > > > If the user-defined function below is put in a file user.cmd, say, then in > > > internal error is generated upon loading it: > > > > I can reproduce too. Have you tried debugging the problem? > > It's due to this change: > > 2009-11-18 Vladimir Prus > > * cli/cli-script.c (process_next_line): Recognize 'end' > even when the line has leading space and we're not parsing > commands. Do you happen to know what is wrong, exactly? Unfortunately, I won't be able to address this until Jan 11, so if you don't have the time to investigate further, I suggest you open an issue in bugzilla. Thanks, Volodya