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 325804 - "invalid pointer: 0x08064650" when quitting
"invalid pointer: 0x08064650" when quitting
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
0.8.x
Other All
: Normal normal
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2006-01-04 22:13 UTC by David (djst) Tenser
Modified: 2006-01-12 19:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David (djst) Tenser 2006-01-04 22:13:49 UTC 
Please describe the problem:
When quitting seahorse, the following text is outputted in the terminal:

** Message: init gpgme version 1.1.0
*** glibc detected *** free(): invalid pointer: 0x08064650 ***


Steps to reproduce:
1. start "seahorse" from a terminal
2. exit the program by closing the window



Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Tested in Ubuntu Dapper 6.04 (development release)
Comment 1 Adam Schreiber 2006-01-05 01:43:49 UTC 
This may be a valid problem.  However, according to Werner Koch libgpgme 1.1.0 is a development branch (see pasted email below).  I also don't think any of the developers are currently using 1.1.0.  Patches are welcome though.

On Mon, 05 Dec 2005 08:46:32 -0600, Rex Dieter said:
>> http://www.gnupg.org/ Says gpgme-1.0.3 is the latest, but gpgme-1.1.0 is 
>> available from the ftp/download site.  Which is the latest (stable) 
>> version?  If 1.0.3, then what is 1.1.0?

Odd minor numbers are commonly used to declare development versions;
thus 1.1.0 is actually a development version.  Anyway, neither API nor
ABI changed and we use 1.1.0 regulary, so there is nothing which
speaks against 1.1.0.

The next version will likely be 1.2.0 however we have to solve some
glib issues for W32 first.

Salam-Shalom,

   Werner
Comment 2 Stef Walter 2006-01-12 19:02:45 UTC 
Thanks for reporting the bug. It was in fact memory being freed in the wrong way. I've fixed the problem (in CVS stable). The fix should be included in 0.8.1.