On Mon, 12 Nov 2007 06:47:06 -, Robert Miller [EMAIL PROTECTED] wrote:
(1) Do you or do you not actually have the same problem when
you build the same code under Linux? You don't say above.
I hadn't had the chance to try yet, but I have now. I can't get it to
give any error in linux
On Nov 12, 9:20 am, William Stein [EMAIL PROTECTED] wrote:
On Mon, 12 Nov 2007 06:47:06 -, Robert Miller [EMAIL PROTECTED] wrote:
(1) Do you or do you not actually have the same problem when
you build the same code under Linux? You don't say above.
Hello,
I hadn't had the
If you want to send me a patch/bundle against 2.8.12 or so and
instructions on how to reproduce this and I will take a look.
Thanks for the offer but I figured out what the problem with my code
was last night, as soon as I started using valgrind.
...
I have seen the issue with gdb printing
On Nov 11, 2007 9:06 PM, Robert Miller [EMAIL PROTECTED] wrote:
I'm working on a new .pyx file, and everything has been working okay,
but something strange is now happening, and I can't quite get to the
bottom of it.
Some side notes- I am running on OS X 10.5, a fresh install of
Questions:
(1) Do you or do you not actually have the same problem when
you build the same code under Linux? You don't say above.
I hadn't had the chance to try yet, but I have now. I can't get it to
give any error in linux at all. All the tests pass, in and out of gdb
mode. I tried
(1) Do you or do you not actually have the same problem when
you build the same code under Linux? You don't say above.
I hadn't had the chance to try yet, but I have now. I can't get it to
give any error in linux at all. All the tests pass, in and out of gdb
mode. I tried several times.
