I'm calling a (standard) module, that is mostly a .pm wrapper around an XS module. The XS code is detecting an error condition and croaking.
The problem is, the traceback from croak stops at the Perl wrapper, and leaves me no clues as to where in my code I am passing bad data.
Is there anyway of persuading croak to give me full traceback? Preferably without digging around in the XS module or having to wait for a perlbug to be actioned to get a patch?
In reply to Getting full traceback from (someone elses) XS routine by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |