<wpwrak>
(unwind=0x6983a0) i'm kinda curious about that myself ;-)
<wpwrak>
(30 min) sorry, took a bit longer
<wpwrak>
(sentinel) of course, 0x82d231c isn't all that much better a value. it's a host address anyway
<wpwrak>
hmm, seems that gdb has a debug option for the DWARF parser, but not for the evaluator. and even the first only operates at the global level. well, i'm quite confident that there's a lot of debug data in that flickernoise executable ...
<wpwrak>
maybe it's time to unearth umlsim :)
<wpwrak>
grmbl. the handling of optimized-out expressions is annoying.  p *info -> Cannot access memory at address 0x0 ("ah, it's a NULL pointer"). but then p info -> $1 = <value optimized out>
<wpwrak>
as a small mercy, we don't seem to have to get into execute_cfa_program. that would be fun to debug. (DWARFS has its own "virtual machine" with instruction set. it then has code snippets to calculate all sorts of things from the registers and memory of the debugged program. last time i checked, the GNU tools, gcc, gdb, etc., only used about 1% of the true power that lies there ;-)
<wpwrak>
just sent further encouragement to faderfox :)
<wolfspraul>
yes seems that exchange is moving now
<wpwrak>
let's hope it goes through before the next set of customs restrictions here. the ones that shut down everything on monday have since been lifted, but they threaten to bring that back
<wpwrak>
"they" = the tax authority. they're working on slapping new controls on customs, basically a triplicate to existing redundant controls. they did something similar to the currency exchange a two weeks ago. see how well it worked: http://fx.sauder.ubc.ca/cgi/fxplot?b=USD&c=ARS&y=daily
<wpwrak>
mwalle: the problem seems to be in the { frame_unwind_register_value (frame=0,regnum=28(sp),...) -> computed bytes=[408d8108] }