freenode/#clasp - IRC Chatlog
Search
14:24:02
drmeister
I just hit a problem that looks like the one that kpoeck is seeing - but in the badge branch that I was about to merge.
14:27:02
drmeister
Interesting observation - I'm doing this on linux and lldb is showing common lisp symbols in the backtraces.
14:28:56
drmeister
lldb is complaining about the DWARF is what it looks like - and we generate DWARF.
14:37:29
Bike
also, i'm still workin on bignum stuff, and i noticed cando uses bignums directly a lot - as in the mpz things, which we will presumably no longer be using
14:39:15
drmeister
I see one place here: https://github.com/cando-developers/cando/blob/master/src/chem/oligomer.cc#L729
14:46:55
drmeister
Bike: my debugging experience here with the undo debugger is very interesting. It's revealing some of the holes in our DWARF generation.
14:47:19
drmeister
CODEGEN-STARTUP-SHUTDOWN^COMPILER^FN^^ (closure=<optimized out>, nargs=<optimized out>, farg0=<optimized out>, farg1=<optimized out>, farg2=<optimized out>, farg3=<optimized out>) at cmpintrinsics.lsp:9999912
14:47:48
drmeister
That looks like one of those cases where I stuck 999999xxx into the origin because I couldn't think of anything better.
14:48:22
drmeister
Of course it's right on instructions that I really, really want to know where they came from.
15:05:11
drmeister
I think another remarkable thing about this debugger is even though variables may be optimized away through much of the code - I should be able to recover them in the registers at particular times when they are used.
15:08:12
Bike
i don't know where the remainder of those are coming from. we should have source info on all instructions originating from compile-file by now. i don't know why this keeps happening.