From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28278 invoked by alias); 22 Aug 2007 13:40:57 -0000 Received: (qmail 26760 invoked by uid 48); 22 Aug 2007 13:40:42 -0000 Date: Wed, 22 Aug 2007 13:40:00 -0000 Message-ID: <20070822134042.26758.qmail@sourceware.org> From: "cagney at redhat dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070822020036.4947.cagney@redhat.com> References: <20070822020036.4947.cagney@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4947] testASMFramelessFunctionReturn(frysk.stepping.TestStepping)ptrace: Input/output error (pt 0x2, pid 15327, addr 0x1524c, data 0x0) X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00330.txt.bz2 List-Id: ------- Additional Comments From cagney at redhat dot com 2007-08-22 13:40 ------- This more selectively enables the virtual stack backtrace (createNonVirtualDebugInfoStackTrace gets confusing as a name), and lets the new work continue. It should probably be enabled in a few more places (but not the stepping engine tests). The underlying problem (or the real bug), looking at the stack backtrace is likely either in libunwind or its binding. The question <> shouldn't result in an exception. Index: frysk-core/frysk/debuginfo/ChangeLog 2007-08-22 Andrew Cagney * DebugInfoStackFactory.java (createDebugInfoStackTrace) (createVirtualStackTrace): Rename createVirtualDebugInfoStackTrace. * TestFrameDebugInfo.java: Update. Index: frysk-core/frysk/hpd/ChangeLog 2007-08-22 Andrew Cagney * CLI.java: Use DebugInfoStackFactory.createVirtualStackTrace. * CoreCommand.java: Ditto. * TestStackCommands.java (testFhpdVirtualStackTrace): Remove unresolved 4947. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4947 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.