[gtkmm] Gtkmm-forge digest, Vol 1 #650 - 1 msg
- From: gtkmm-forge-request lists sourceforge net
- To: gtkmm-forge lists sourceforge net
- Subject: [gtkmm] Gtkmm-forge digest, Vol 1 #650 - 1 msg
- Date: Mon, 22 Mar 2004 20:02:40 -0800
Send Gtkmm-forge mailing list submissions to
gtkmm-forge lists sourceforge net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
gtkmm-forge-request lists sourceforge net
You can reach the person managing the list at
gtkmm-forge-admin lists sourceforge net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."
gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla. A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.
Today's Topics:
1. [Bug 137030] Changed - signal_timeout() causes a critical warning (bugzilla-daemon widget gnome org)
--__--__--
Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, murrayc murrayc com
Cc:
Date: Mon, 22 Mar 2004 05:55:59 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 137030] Changed - signal_timeout() causes a critical warning
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=137030
Changed by pavenis latnet lv
--- shadow/137030 Sat Mar 20 14:13:42 2004
+++ shadow/137030.tmp.22035 Mon Mar 22 05:55:59 2004
@@ -52,6 +52,32 @@
------- Additional Comments From martin-ml hippogriff de 2004-03-20 09:39 -------
Should be fixed in cvs. Please confirm and close the bug.
------- Additional Comments From murrayc murrayc com 2004-03-20 14:13 -------
Yes, that fixes it. Thanks, Martin, and well done.
+
+------- Additional Comments From pavenis latnet lv 2004-03-22 05:55 -------
+Have You run text example under Valgrind?
+
+At least valgrind-2.1.0 return messages about invalid free() for me
+(when exitting test example), but no more earlier critical message:
+
+==5442== Invalid free() / delete / delete[]
+==5442== at 0x400293F9: free (vg_replace_malloc.c:186)
+==5442== by 0x40BE099B: (within /lib/libc-2.3.2.so)
+==5442== by 0x40BE0708: __libc_freeres (in /lib/libc-2.3.2.so)
+==5442== by 0x4016893C: vgPlain___libc_freeres_wrapper
+(vg_intercept.c:172)
+==5442== by 0x40AFE68F: exit (in /lib/libc-2.3.2.so)
+==5442== by 0x40AE893D: __libc_start_main (in /lib/libc-2.3.2.so)
+==5442== by 0x804C2C0:
+(within /disk2/src/bugs/gtkmm/timeout_test_case)
+==5442== Address 0x40AD27E8 is not stack'd, malloc'd or free'd
+==5442==
+=
+
+I'm not getting similar error message when running test examples of
+today's CVS version of glibmm under the same version of valgrind.
+
+Andris
+
--__--__--
_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]