[Bug 163] New: SIGQUIT handler should dump stack for all threads, not just "current thread"
[email protected] Sun, 11 Dec 2005 10:32:31 -0500
| Newsgroups | gmane.comp.java.vm.sablevm.bugs |
|---|---|
| Message-ID | <[email protected]> |
http://sablevm.org/bugs/show_bug.cgi?id=163
Summary: SIGQUIT handler should dump stack for all threads, not
just "current thread"
Product: SableVM
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: default
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
The SIGQUIT handler seems to dump a stack trace for just the current thread, in
sablevm 1.13-pre1. That's not very helpful when you're trying to debug
multi-threading-related problems.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.