I know nothing about parrot (although it looks interesting!) - but from this set of slides (http://www.jnthn.net/papers/2005-lpw-parrot-slides.pdf) and your compilation flags, it looks like your parrot runtime dispatches parrot opcodes by using computed gotos rather than true C function calls. Thus I guess it would make sense that ustack() doesn't work as expected, as these aren't regular symbols.
Interesting that gdb appears to work though - a complete guess, but as the computed goto appears to be a gcc-specific, perhaps gdb has specialised support for this too. -- Philip Beevers Chief Architect - Fidessa mailto:[EMAIL PROTECTED] phone: +44 1483 206571 ******************************************************************************************************************************************************************************************** This message is intended only for the stated addressee(s) and may be confidential. Access to this email by anyone else is unauthorised. Any opinions expressed in this email do not necessarily reflect the opinions of Fidessa. Any unauthorised disclosure, use or dissemination, either whole or in part is prohibited. If you are not the intended recipient of this message, please notify the sender immediately. Fidessa plc - Registered office: Dukes Court, Duke Street, Woking, Surrey, GU21 5BH, United Kingdom Registered in England no. 3781700 VAT registration no. 688 9008 78 Fidessa group plc - Registered Office: Dukes Court, Duke Street, Woking, Surrey, GU21 5BH, United Kingdom Registered in England no. 3234176 VAT registration no. 688 9008 78 _______________________________________________ dtrace-discuss mailing list [email protected]
