[Matplotlib-users] segmentation fault when saving images

Discussion:

Gabriele Brambilla

2015-03-19 17:13:06 UTC

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: RuntimeWarning: divide by zero encountered in divide

lwb = 5/(np.log10(modB.max()/modB))

Bdipole.py:55: RuntimeWarning: divide by zero encountered in divide

lwe = 5/(np.log10(modE.max()/modE))

Segmentation fault

Thanks

Gabriele

Paul Hobson

2015-03-19 17:17:18 UTC

Permalink

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

Benjamin Root

2015-03-19 17:19:31 UTC

Permalink

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/latest/

Ben Root

As a side-note: faulthandler is part of the standard library as of 3.3!
Neat!

On Thu, Mar 19, 2015 at 1:13 PM, Gabriele Brambilla <

Post by Gabriele Brambilla
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.
[gs66-stumbras:~/Desktop] gbrambil% python Bdipole.py
Bdipole.py:52: RuntimeWarning: divide by zero encountered in divide
lwb = 5/(np.log10(modB.max()/modB))
Bdipole.py:55: RuntimeWarning: divide by zero encountered in divide
lwe = 5/(np.log10(modE.max()/modE))
Segmentation fault
Thanks
Gabriele
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for
all
things parallel software development, from weekly thought leadership blogs
to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Matplotlib-users mailing list
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Gabriele Brambilla

2015-03-19 17:27:34 UTC

Permalink

Actually Paul Hobson was right.

Now it works.

Thanks

Gabriele

Post by Benjamin Root
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/latest/
Ben Root
As a side-note: faulthandler is part of the standard library as of 3.3!
Neat!
On Thu, Mar 19, 2015 at 1:13 PM, Gabriele Brambilla <

Post by Gabriele Brambilla
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.
[gs66-stumbras:~/Desktop] gbrambil% python Bdipole.py
Bdipole.py:52: RuntimeWarning: divide by zero encountered in divide
lwb = 5/(np.log10(modB.max()/modB))
Bdipole.py:55: RuntimeWarning: divide by zero encountered in divide
lwe = 5/(np.log10(modE.max()/modE))
Segmentation fault
Thanks
Gabriele
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub
for all
things parallel software development, from weekly thought leadership
blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Matplotlib-users mailing list
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Benjamin Root

2015-03-19 17:32:07 UTC

Permalink

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 <

Post by Gabriele Brambilla
Actually Paul Hobson was right.
Now it works.
Thanks
Gabriele

Post by Benjamin Root
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/latest/
Ben Root
As a side-note: faulthandler is part of the standard library as of 3.3!
Neat!
On Thu, Mar 19, 2015 at 1:13 PM, Gabriele Brambilla <

Post by Gabriele Brambilla
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.
[gs66-stumbras:~/Desktop] gbrambil% python Bdipole.py
Bdipole.py:52: RuntimeWarning: divide by zero encountered in divide
lwb = 5/(np.log10(modB.max()/modB))
Bdipole.py:55: RuntimeWarning: divide by zero encountered in divide
lwe = 5/(np.log10(modE.max()/modE))
Segmentation fault
Thanks
Gabriele
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub
for all
things parallel software development, from weekly thought leadership
blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Matplotlib-users mailing list
https://lists.sourceforge.net/lists/listinfo/matplotlib-users