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/5527] New: testStepSigReturn(frysk.proc.TestTaskObserverInstructionSigReturn)junit.framework.AssertionFailedError: Wrong signal received: 5
Date: Sat, 29 Dec 2007 04:18:00 -0000 [thread overview]
Message-ID: <20071229041822.5527.cagney@redhat.com> (raw)
For -arch 32:
testStepSigReturn(frysk.proc.TestTaskObserverInstructionSigReturn)junit.framework.AssertionFailedError:
Wrong signal received: 5
at frysk.proc.TestTaskObserverInstructionSigReturn.updateSignaled(TestRunner)
at frysk.proc.Task.notifySignaled(TestRunner)
at frysk.proc.live.LinuxTaskState$Running.handleSignaledEvent(TestRunner)
at frysk.proc.live.LinuxTaskState$Stepping.handleSignaledEvent(TestRunner)
at frysk.proc.live.LinuxTaskState$Stepping.handleTrappedEvent(TestRunner)
at frysk.proc.live.LinuxTask.processTrappedEvent(TestRunner)
at frysk.proc.live.LinuxWaitBuilder.stopped(TestRunner)
at frysk.sys.Wait.wait(TestRunner)
at frysk.sys.Wait.waitAll(TestRunner)
at frysk.event.WaitEventLoop.block(TestRunner)
at frysk.event.EventLoop.runEventLoop(TestRunner)
at frysk.event.EventLoop.runPolling(TestRunner)
at frysk.testbed.TestLib.assertRunUntilStop(TestRunner)
at frysk.testbed.TestLib.assertRunUntilStop(TestRunner)
at frysk.proc.TestTaskObserverInstructionSigReturn.testStepSigReturn(TestRunner)
at frysk.junit.Runner.runCases(TestRunner)
at frysk.junit.Runner.runTestCases(TestRunner)
at TestRunner.main(TestRunner)
the log shows:
FINE: entering peekFully, caret: 0x380, off: 0x0, len: 0x4
28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully
FINE: exiting peekFully
28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully
FINE: entering peekFully, caret: 0x80, off: 0x0, len: 0x4
28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully
FINE: exiting peekFully
28-Dec-07 10:32:19 PM frysk.proc.Task notifyCodeBreakpoint
FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping}
notifyCodeBreakpoint(134,514,034)
28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully
FINE: entering peekFully, caret: 0x80, off: 0x0, len: 0x4
28-Dec-07 10:32:19 PM inua.eio.ByteBuffer peekFully
FINE: exiting peekFully
28-Dec-07 10:32:19 PM frysk.proc.Task getMemory
FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping}
entering get memory frysk.proc.live.LogicalMemoryBuffer@2f89d735
28-Dec-07 10:32:19 PM frysk.proc.Task getMemory
FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping}
exiting get memory frysk.proc.live.LogicalMemoryBuffer@2f89d735
28-Dec-07 10:32:19 PM frysk.proc.live.LinuxTaskState$Stepping handleSignaledEvent
FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping}
handleSignaledEvent, signal: 5
28-Dec-07 10:32:19 PM frysk.proc.live.LinuxTaskState$Running handleSignaledEvent
FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping}
handleSignaledEvent, signal: 5
28-Dec-07 10:32:19 PM frysk.proc.Task notifySignaled
FINE: {frysk.proc.live.LinuxTask@2fa2d355,pid=14074,tid=14074,state=stepping}
notifySignaled(int)
--
notice reasoning that it got a sig-trap for no reason.
machine is amd64 running kernel 2.6.23.9-85.fc8; doesn't occur on intel64
running kernel 2.6.23.1-42.fc8
--
Summary: testStepSigReturn(frysk.proc.TestTaskObserverInstruction
SigReturn)junit.framework.AssertionFailedError: Wrong
signal received: 5
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: cagney at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5527
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-12-29 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 4:18 cagney at redhat dot com [this message]
2007-12-29 5:19 ` [Bug general/5527] " cagney at redhat dot com
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=20071229041822.5527.cagney@redhat.com \
--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).