On Mon, Aug 1, 2011 at 8:30 AM, Andreas Kloeckner <[email protected]> wrote: > What it likely means to say is that your kernel caused a segmentation > fault. Check the output of 'dmesg'. If it says something like 'Nv Xid > 13' (from memory, may be wrong--the 13 is what says 'segfault', I > think), then that's what it is. Have you tried chopping your kernel down > to almost-nothing? Bisected?
As it turns out, chopping it down was part of the issue - I was passing in too many arguments to the kernel from the python side. :( Would it be possible to improve the error reporting for these kinds of errors, or is this something that's baked into the CUDA libraries? I'd be willing to at least try my hand at a patch, if you think it's possible. Knowing how to check for in-kernel segfaults is great - thank you for that! :) Cheers, Eli _______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
