This is the mail archive of the
frysk-bugzilla@sourceware.org
mailing list for the frysk project.
[Bug general/4947] testASMFramelessFunctionReturn(frysk.stepping.TestStepping)ptrace: Input/output error (pt 0x2, pid 15327, addr 0x1524c, data 0x0)
- From: "cagney at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: frysk-bugzilla at sourceware dot org
- Date: 22 Aug 2007 13:40:42 -0000
- Subject: [Bug general/4947] testASMFramelessFunctionReturn(frysk.stepping.TestStepping)ptrace: Input/output error (pt 0x2, pid 15327, addr 0x1524c, data 0x0)
- References: <20070822020036.4947.cagney@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- 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 <<is this a signal
frame>> shouldn't result in an exception.
Index: frysk-core/frysk/debuginfo/ChangeLog
2007-08-22 Andrew Cagney <cagney@redhat.com>
* DebugInfoStackFactory.java (createDebugInfoStackTrace)
(createVirtualStackTrace): Rename
createVirtualDebugInfoStackTrace.
* TestFrameDebugInfo.java: Update.
Index: frysk-core/frysk/hpd/ChangeLog
2007-08-22 Andrew Cagney <cagney@redhat.com>
* 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.