After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678445 - std::logic_error thrown ("basic_string::_S_construct null not valid")
std::logic_error thrown ("basic_string::_S_construct null not valid")
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: pan-maint
pan-maint
Depends on:
Blocks:
 
 
Reported: 2012-06-20 06:37 UTC by Dominique Dumont
Modified: 2012-06-30 07:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Dumont 2012-06-20 06:37:09 UTC 
Hello

A Debian user is reporting that Pan 0.137 (64 bits) crashes with the following error:

Program received signal SIGABRT, Aborted.
0x00007ffff3927475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.

This crash does not occur if the user moves ~/.pan2 out if the way. The content
of this directory can be made available if needed.

For more details and full stack trace, see the original bug report:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678117

All the best
Comment 1 Sam Morris 2012-06-20 09:26:42 UTC 
I was the original reporter. Let me know if you need any extra info.
Comment 2 Heinrich Müller 2012-06-20 20:32:41 UTC 
Should be fixed in the newest git. Please check and if not valid, reopen.
Comment 3 Sam Morris 2012-06-21 01:52:18 UTC 
This is difficult to check as I can't even reproduce the crash if I build pan myself! It only happens when I run the binary provided by Debian.
Comment 4 Heinrich Müller 2012-06-21 15:41:16 UTC 
Well, then I fixed it because somebody else ran into the same problem. I'm just saying, if you ever encounter this with a binary release newer than the one you have, feel free to reopen this bug.
Comment 5 Sam Morris 2012-06-21 17:07:51 UTC 
Ok will do, thanks. :)
Comment 6 Dominique Dumont 2012-06-21 18:54:21 UTC 
Hmm looks like I've missed 0.138 release.

I'll package it soon for Debian.

Since Debian freeze is imminent (June 30th), I'll try to backport Heinrich's fix so that the bug is closed for next Debian release. Unless a new pan can be released before that.

All the best
Comment 7 Heinrich Müller 2012-06-22 13:21:54 UTC 
I'll package 0.139 soon, before the freeze.
Comment 8 Dominique Dumont 2012-06-29 07:33:04 UTC 
Hello Heinrich

What are the news on 0.139 release ?

I don't like rushing people who work on their free time, but Debian freeze is scheduled for tomorrow, and I need some time to package 0.139. 

(I've prepared a 0.138 package in case I don't have time to handle 0.139 before tomorrow evening)

All the best
Comment 9 Heinrich Müller 2012-06-29 22:13:57 UTC 
I'll package it and update the homepage today (30th) middays. If that's too late I'm sorry, but I had other things to do. Let me know if it's still OK for you.
Comment 10 Dominique Dumont 2012-06-30 07:28:42 UTC 
Assuming you live in Europe, I should be able to upload the package in the afternoon or evening.

Thanks