Thanks for all the reply.
I hope that anyone know a good way to debug cython "Python-like" code
without using insert print statements.
> I should have googled before I replied:
>
> http://docs.cython.org/src/userguide/debugging.html
Before I post the question I had take a look it the link above
On Nov 12, 12:33 pm, Nils Bruin wrote:
> Does this need a "cydb" wrapper around gdb or does gdb have its
> own customization options that allow something along these lines?
I should have googled before I replied:
http://docs.cython.org/src/userguide/debugging.html
It would be great if someone w
On Nov 12, 12:08 pm, Jason Grout wrote:
> I think you can also use gdb; it seems I've done it once before, at least.
I have used gdb for stack examination after a segfault. For "C-like"
pieces of Cython it works quite well. For "Python-like" pieces it's
horrible, because python objects are virtua
On Mon, Nov 12, 2012 at 12:08 PM, Jason Grout
wrote:
> On 11/12/12 12:26 PM, Raniere Gaia Silva wrote:
>>
>> Hi,
>> how is the easy way to debug a Cython code?
>
>
> I insert print statements, think really hard, insert more print statements,
> etc.
This is what I typically do.
> I think you can
On 11/12/12 12:26 PM, Raniere Gaia Silva wrote:
Hi,
how is the easy way to debug a Cython code?
I insert print statements, think really hard, insert more print
statements, etc.
I think you can also use gdb; it seems I've done it once before, at least.
Thanks,
Jason
--
You received this m
