Search
Sunday, 2nd of April 2023, 21:35:52 UTC
21:46:54
Bike
sso i did a quick little test of having a bytecode function call ERROR while i go in with gdb, and it looks like the pc is actually available already (it's just about the only thing that is, though)
23:02:34
drmeister
From where do you get it?
0:07:27
drmeister
That there's debug info - you can't trust that. Or maybe we can???
0:09:07
drmeister
Could we check if debug info is available for the ip at every instruction?
0:13:50
drmeister
We should be able to scan the DWARF and identify if we can obtain the IP at every instruction.
0:50:22
Bike
we could do the llvm-dwarfdump i guess
0:50:46
Bike
the debug info is definitely there in at least one place
2:16:46
Bike
alright, took me a while to figure out llvm-dwarfdump but i see the line table now. it looks reasonably extensive
2:18:20
Bike
http://ix.io/4sxM Behold
2:18:51
Bike
obtained with `llvm-dwarfdump path/to/iclasp --name pc` and then looking for the right file and line
2:20:00
Bike
i guess this means it is in various registers at times, so that's good
2:23:33
Bike
would be kind of cool to have a tool that displays source with dwarf annotations so you can see where variables end up.
2:24:04
Bike
there are a few holes in the table tho, i think. near the end.
2:28:24
Bike
--statistics is also interesting, on a tangential note... it gives an idea of how good the debugging coverage is overall
2:29:15
Bike
for example i'm seeing that about 29% of variables have locations at least half the time
2:30:04
Bike
also we have like three million variables, wow.
Monday, 3rd of April 2023, 9:35:52 UTC