This is the mail archive of the
frysk-bugzilla@sourceware.org
mailing list for the frysk project.
[Bug general/4237] WARNING: {frysk.proc.LinuxPtraceTask@32b28d75,pid=32138,tid=32138,state=running} Unhandled real stop event
- From: "mark at klomp dot org" <sourceware-bugzilla at sourceware dot org>
- To: frysk-bugzilla at sourceware dot org
- Date: 17 Apr 2008 21:37:46 -0000
- Subject: [Bug general/4237] WARNING: {frysk.proc.LinuxPtraceTask@32b28d75,pid=32138,tid=32138,state=running} Unhandled real stop event
- References: <20070321162450.4237.mcvet@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mark at klomp dot org 2008-04-17 21:37 -------
The warning still happens from time to time. I suspect that it is seeing a
double attach somehow. The warning is annoying because I was unable to track it
fully down. The good news is that the the test mentioned does consistently PASS
now. This was a more complex version the testFirstFrameInSignalHandler() test.
The test needed to be adjusted slightly to make sure the first line of the
signal handler was identified correctly:
commit 6356571eaff4020746159c99704b3dbaa14bc221
Author: Mark Wielaard <mwielaard@redhat.com>
Date: Thu Apr 17 23:33:53 2008 +0200
Don't mark TestStepping.testStepSigRaise() as unresolved bug #4237.
frysk-core/frysk/pkglibdir/ChangeLog
2008-04-17 Mark Wielaard <mwielaard@redhat.com>
* funit-rt-sigraise.c (handler): Make sure entry marker is really on
first source line.
frysk-core/frysk/stepping/ChangeLog
2008-04-17 Mark Wielaard <mwielaard@redhat.com>
* TestStepping.java (testStepSigRaise): Don't mark unresolved #4237.
Leaving bug open because the warning is still annoying as long as we haven't
figured out where the extra stop event is coming from.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|mark at klomp dot org |frysk-bugzilla at sourceware
| |dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=4237
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.