There is a shell of a pike debugger called unbug, but it's of limited use in these situations, as breaking and stepping is clumsy or non-existent.
That said, I've fiddled with it, and it works to a certain extent for certain tasks.
There is a bounty ($$$) out for implementation of step and break opcodes. If there's anyone out there with this kind of skill, do contact me.
Bill
On Fri, 2 Mar 2007, Saqib Saleem wrote:
Ok! And is there any way where I can tell pike to execute the .pike file line by line so I can see whats happening. Currenlty my program is stuck in 10 recursive loops. And trace is really throwing each and everything and so does the werror is gonna do.
Regards Saqib
On 2/3/07 15:05, "Mirar @ Pike importmöte för mailinglistan" 6341@lyskom.lysator.liu.se wrote:
As I said, the werror method is usually very sufficient and you can print whatever you want. The "%O" format descriptor can print any value, so it will not crash on that.
-- Saqib Saleem
Metro International 3rd Floor, Interpark House 7 Down Street London W1J 7AJ United Kingdom
Email: saqib.saleem@metro.lu Telephone: +44 20 7016 1354 Mobile: +44 78 4167 2857 Fax: +44 20 7016 1400
!DSPAM:45e83e5b117541922123026!