well, that still doesn't explain the segfaults. NaNs shouldn't cause
matplotlib to crash upon saving. I would still be interested in a
stacktrace.
Ben
On Thu, Mar 19, 2015 at 1:27 PM, Gabriele Brambilla <
gb.gabrielebrambi...@gmail.com> wrote:
> Actually Paul Hobson was right.
>
> Now it works.
Actually Paul Hobson was right.
Now it works.
Thanks
Gabriele
On Thu, Mar 19, 2015 at 1:19 PM, Benjamin Root wrote:
> The warnings probably have nothing to do with the issue at hand. Try this.
> Install the package "faulthandler" and add the appropriate lines to your
> Bdipoly.py script and r
The warnings probably have nothing to do with the issue at hand. Try this.
Install the package "faulthandler" and add the appropriate lines to your
Bdipoly.py script and run it again. That way, we can get a traceback and
find out where it is segfaulting from.
http://faulthandler.readthedocs.org/en
What happens when you edit your program to avoid dividing by zero?
-p
—
Sent from Mailbox
On Thu, Mar 19, 2015 at 10:14 AM, Gabriele Brambilla
wrote:
> Hi guys,
> I don't understand why now, after I save an image when it is prompted out,
> the image is not saved and it closes automatically a
Hi guys,
I don't understand why now, after I save an image when it is prompted out,
the image is not saved and it closes automatically and on the terminal
appears segmentation fault.
this is what my terminal shows:
[gs66-stumbras:~/Desktop] gbrambil% python Bdipole.py
Bdipole.py:52: RuntimeWarn
