freenode/#sbcl - IRC Chatlog
Search
11:16:44
hlavaty
hi on windoes, is there a way to get pid for run-program process, which is suitable for taskkill? sb-ext:process-pid gives a number which doesn't seem to be windows pid
11:20:07
jackdaniel
hlavaty: I believe that it is meant to be killed with sb-ext:process-close called on the return value of sb-ext:run-program
11:24:51
hlavaty
actually it looks like sb-ext:process-pid returns handle for which GetProcessID returns the actual pid
11:32:01
jackdaniel
then maybe (defun terminate-win-process (pid) (sb-ext:run-program "taskkill" '(…))) ;? if pid is correct
11:32:46
hlavaty
jackdaniel: yes, but as i said initially, sb-ext:process-pid doesn't return the pid
11:33:24
hlavaty
we'll try sb-ext:process-pid -> handle -> GetProcessId -> pid -> taskkill and see if it works
11:34:01
scymtym
hlavaty: maybe try this via sb-alien: https://msdn.microsoft.com/en-us/library/ms686714(VS.85).aspx
11:35:17
hlavaty
scymtym: yeah that is an option, although it doesnt seem to advertise killing the whole process subtree
11:39:15
scymtym
unless the signal is SIGTERM or SIGINT and the child process takes care of it itself
12:16:08
stassats
the hppa build is broken because it has an ldb instruction, the new instruction format defines functions => conflict
12:42:34
stassats
failed AVER: (= (LOGAND (SB!FASL::DESCRIPTOR-BITS #) SB!VM:WIDETAG-MASK) SB!VM:SIMPLE-FUN-WIDETAG)
14:25:25
stassats
frame #15: 0x0000000009aaa84f sbcl`set_forwarding_pointer(pointer=0x0000000009aaa84f, newspace_copy=165909120) at forwarding-ptr.h:55
15:39:33
|3b|
ACTION thought i'd seen it discussed before, but can't find it in the logs... how hard would it be to make sbcl generate/maintain windows-style unwind info? (doesn't have to be 100%, since i just want it for profiling rather than actual real unwinding)
15:40:24
|3b|
from what i could see, main parts would be dealing with things moving during GC (assuming functions move?) and generating the stuff for interpreting function entry/exit code... might be missing things though
15:41:24
|3b|
ACTION is finding profile info with no caller info annoying (though still much better than no profile info)
15:42:34
|3b|
"2 "foreign function NtQueryInformationThread" 36.04 36.04 85.01" for example could use some more context :)
15:51:33
|3b|
also, is there any way to get the windows thread id from an sbcl thread? so far i've just been interrupting other thread and getting the thread id there, but that's pretty ugly.
16:24:47
stassats
although -O0 is not a default but i'm sure there's an actual problem and it'll come back to hunt us