|
08:03
tellable6__ joined,
linkable6__ joined
08:05
sourceable6__ joined,
coverable6__ joined,
benchable6__ joined
08:09
linkable6 left,
tellable6 left,
sourceable6 left,
coverable6 left,
benchable6 left
08:25
leont_ joined
08:31
leont left,
leont_ is now known as leont
|
|||
| patrickb | o/ | 12:44 | |
| I've started using the debugserver file loaded notifications with the suspend flag. Whenever I receive such a notification, I do a quick introspection (usually without any debug protocol action) and then resume the thread again. | 12:45 | ||
| But most of the time the threads don't resume and the debug server logs print: "success resuming thread; its status is now 2". Status 2 is MVMGCStatus_UNABLE. | 12:46 | ||
| I suspect the GCStatus handling is somehow broken, but I still have too little of an idea how the GC status' are meant to work to trace the error in a directed manner. Any pointers are highly appreciated... | 12:50 | ||
| I notice that MVM_debugserver_request_thread_suspends moves the GCStatus from NONE -> INTERRUPTED|SUSPEND_REQUEST, while notify_new_file moves it from NONE -> NONE|SUSPEND_REQUEST. Is that difference intentional? | 13:49 | ||
| gc/orchestrate.c signal_one_thread also does not account for NONE|SUSPEND_REQUEST, only for INTERRUPT|SUSPEND_REQUEST. | 14:07 | ||
| I start to suspect again, that NONE|SUSPEND_REQUEST is not a valid status. | 14:08 | ||
|
15:55
[Coke] left
17:49
[Coke] joined
|
|||