From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4876 invoked by alias); 29 Apr 2011 16:27:10 -0000 Received: (qmail 4834 invoked by uid 22791); 29 Apr 2011 16:27:09 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 Apr 2011 16:26:57 +0000 From: "stephan.kramer at imperial dot ac.uk" To: gdb-prs@sourceware.org Subject: [Bug fortran/11354] error in evaluating variable length fortran strings causes stalls X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephan.kramer at imperial dot ac.uk X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.1 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Fri, 29 Apr 2011 16:27:00 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2011-q2/txt/msg00252.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=11354 --- Comment #3 from Stephan Kramer 2011-04-29 16:26:39 UTC --- Thanks for your response. I know proper modern fortran support is a more longterm issue - really appreciate the effort that needs to go into that. Hitting ctrl-c doesn't solve the issue as that breaks off printing the frame info before even printing the line number, which rather limits the functionality of gdb: no backtraces, no line numbers when stepping through the code. When you say I don't see this issue with fsf gdb, do you mean it doesn't stall? Or, do you not see "Cannot access memory at address ". It's the latter that is the real issue, because that causes the stalls in executables with a large memory layout (not the example program of course); basically goes through the lot of it before giving up. I still see this behaviour with gdb version 7.2 on Ubuntu Natty. Once again, the issue is not the faulty printing. We know we can work around this with some pointer voodoo, it's the stalling that's causing us some real headaches trying to debug things on a large executable. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.