BrowserUk has asked for the wisdom of the Perl Monks concerning the following question:
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?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Getting full traceback from (someone elses) XS routine
by borisz (Canon) on Feb 15, 2005 at 01:49 UTC | |
|
Re: Getting full traceback from (someone elses) XS routine
by borisz (Canon) on Feb 15, 2005 at 00:51 UTC | |
by BrowserUk (Patriarch) on Feb 15, 2005 at 01:05 UTC | |
by tye (Sage) on Feb 15, 2005 at 02:08 UTC | |
by borisz (Canon) on Feb 15, 2005 at 01:12 UTC |