It looks like barf() has to try a bit harder to unwind the call stack until it hits the first function that is not in the PDL namespace.
On Sep 22, 2010, at 4:39 PM, Chris Marshall wrote: > Many slice operations don't actually happen until the > result is required for further processing. As a result, > the error reports can be separated from the actual > code with the problem. > > Do you have an example code that fails to report the > location of where the bad code was called? I've also > had success by running problem code under the perl -d > debugger to get more information at runtime. > > --Chris > > On 9/22/2010 1:32 PM, Ingo Schmid wrote: >> >> when some index overflows, PDL prints a message like this, ... >> >> Slice cannot start or end above limit at >> /usr/lib64/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi/PDL/Core.pm >> line 477. > > _______________________________________________ > Perldl mailing list > [email protected] > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl -- Tim Jenness _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
