Hi everyone, :-)
I interested in using Clozure Common Lisp[1] on SmartOS, and want to benefit
from all the nice debugging/observation capabilities offered by the OS. To that
end I ended up writing a ustack helper for CCL. Needless to say, I didn’t get
it right the first time, and now I need to debug it.
I’m having some well-known issues with that. :-) I already received some lovely
help via IRC, but I think I could use some more pointers, specifically
regarding the kernel’s dtrace_helptrace.
I see multiple paths that I imagine would help me forward:
1) write an mdb script that makes the dtrace_helptrace... useful to me. I.e.
resolve the addresses(?) printed by it to strings from the original D
source. (realistic)
2) add some kind of trace function to debug D scripts (printf style
debugging), or even make printf work inside ustack helpers. (I understand
there are reasons why printf does *not* work inside ustack helpers, but
still...)
3) create an interactive D REPL that can attach to core dumps for interactive
prototyping. (as a Lisp programmer this would be the promised land for me,
but I understand that its a non-trivial task)
I am willing to put in some work to accomplish either of these. As I know next
to nothing about SmartOS, yet, I would appreciate any hints and pointers. And
of course, I might have missed existing facilities that would help me out.
Cheers,
Max
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
