On Fri, 2006-08-04 at 13:25 +0200, gwenj wrote:
Hello,
I use gtk+ for my soft's graphic interface.
But valgrind make an log file containing approximately 22700 lines for an
simple source code like :
#include gtk/gtk.h
int main(int argc, char **argv) {
gtk_init(argc, argv);
On Sun, Aug 06, 2006 at 09:45:00AM +0200, Iago Rubio wrote:
I've just compiled and run this code snippet with valgrind, and the
results are on my system (Fedora):
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 12 from 1)
malloc/free: in use at exit: 0 bytes in 0 blocks.
malloc/free:
On Sun, 06 Aug 2006 13:53:46 +0200
Iago Rubio [EMAIL PROTECTED] wrote:
On Sun, 2006-08-06 at 11:37 +0200, gwenhael wrote:
On Sun, 06 Aug 2006 09:45:00 +0200
Iago Rubio [EMAIL PROTECTED] wrote:
On Fri, 2006-08-04 at 13:25 +0200, gwenj wrote:
Hello,
I use gtk+ for my soft's
On Sun, 6 Aug 2006, Iago Rubio wrote:
The 'possibly lost' bites means - AFAIK - that exists pointers to the
interior of the analyzed block that may have pointed to the start of the
block and have been moved, among other possible causes, such as debug
padding - where a pointer to an object is
On Sun, 06 Aug 2006 09:45:00 +0200
Iago Rubio [EMAIL PROTECTED] wrote:
On Fri, 2006-08-04 at 13:25 +0200, gwenj wrote:
Hello,
I use gtk+ for my soft's graphic interface.
But valgrind make an log file containing approximately 22700 lines for an
simple source code like :
#include
On Sun, 06 Aug 2006 13:53:46 +0200
Iago Rubio [EMAIL PROTECTED] wrote:
On Sun, 2006-08-06 at 11:37 +0200, gwenhael wrote:
On Sun, 06 Aug 2006 09:45:00 +0200
Iago Rubio [EMAIL PROTECTED] wrote:
On Fri, 2006-08-04 at 13:25 +0200, gwenj wrote:
Hello,
I use gtk+ for my soft's
On Sun, 2006-08-06 at 11:38 +0200, David Nečas (Yeti) wrote:
On Sun, Aug 06, 2006 at 09:45:00AM +0200, Iago Rubio wrote:
I've just compiled and run this code snippet with valgrind, and the
results are on my system (Fedora):
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 12 from
On Sun, 2006-08-06 at 14:07 +0200, gwenj wrote:
The result to valgrind is :
==29096== LEAK SUMMARY:
==29096==definitely lost: 0 bytes in 0 blocks.
Nothing malloc'ed and not freed.
==29096== possibly lost: 800 bytes in 20 blocks.
This may be investigated further, but I bet they are
==29096==still reachable: 41,380 bytes in 618 blocks.
That's completely normal. Surely they're static variables holding
pointers to freed memory.
maybe this comes from glib memory allocator. I have such results with
gstreamer too
Vincent
___
On Sun, 2006-08-06 at 20:55 +0200, Vincent Torri wrote:
==29096==still reachable: 41,380 bytes in 618 blocks.
That's completely normal. Surely they're static variables holding
pointers to freed memory.
maybe this comes from glib memory allocator. I have such results with
Hello,
I use gtk+ for my soft's graphic interface.
But valgrind make an log file containing approximately 22700 lines for an
simple source code like :
#include gtk/gtk.h
int main(int argc, char **argv) {
gtk_init(argc, argv);
GtkWidget *win= gtk_window_new(GTK_WINDOW_TOPLEVEL);
Hello,
I use gtk+ for my soft's graphic interface.
But valgrind make an log file containing approximately 22700 lines for an
simple source code like :
#include gtk/gtk.h
int main(int argc, char **argv) {
gtk_init(argc, argv);
GtkWidget *win= gtk_window_new(GTK_WINDOW_TOPLEVEL);
12 matches
Mail list logo
