On Sat, Nov 15, 2008 at 11:31 AM, James E Keenan <[EMAIL PROTECTED]> wrote: > chromatic wrote: >> >> On Tuesday 28 October 2008 20:07:18 James Keenan via RT wrote: >> >>> Still failing as of r32225; cf >>> http://smolder.plusthree.com/app/public_projects/tap_stream/7437/260 >>> >>> not ok 6 - set_integer_keyed_str >>> >>> # Failed test 'set_integer_keyed_str' >>> # at t/pmc/packfile.t line 140. >>> # Exited with error code: [SIGNAL 11] >>> # Received: >>> # >>> # Expected: >>> # not equal >>> # >> >> Can you post a backtrace? >> >> -- c > > Have been on vacation with poor net access, so I haven't been able to > respond to much. > > I don't actually know how to do a backtrace. Can you instruct or post link > to how this would interact with 'perl thistest' or 'prove thistest'? > > Thank you very much. > > kid51 >
gdb ./parrot gdb> run t/pmc/packfile_XX.pir # xx = whichever test is the one that failed When parrot explodes again: gdb> bt This generates a backtrace (showing the state of the C runtime when the explosion occurred.) Thanks! -- Will "Coke" Coleda
