public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4947] testASMFramelessFunctionReturn(frysk.stepping.TestStepping)ptrace: Input/output error (pt 0x2, pid 15327, addr 0x1524c, data 0x0)
Date: Wed, 22 Aug 2007 13:40:00 -0000 [thread overview]
Message-ID: <20070822134042.26758.qmail@sourceware.org> (raw)
In-Reply-To: <20070822020036.4947.cagney@redhat.com>
------- 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.
prev parent reply other threads:[~2007-08-22 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 2:00 [Bug general/4947] New: " cagney at redhat dot com
2007-08-22 2:48 ` [Bug general/4947] " cagney at redhat dot com
2007-08-22 13:40 ` cagney at redhat dot com [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070822134042.26758.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).