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 163639 - *** glibc detected *** free(): invalid pointer: 0xbfffd3d0 ***
*** glibc detected *** free(): invalid pointer: 0xbfffd3d0 ***
Status: RESOLVED INCOMPLETE
Product: gnome-nettool
Classification: Applications
Component: general
0.99.x
Other All
: High critical
: ---
Assigned To: Germán Poo-Caamaño
Rodrigo Moya
Depends on:
Blocks:
 
 
Reported: 2005-01-11 10:45 UTC by Marcin Krzyzanowski
Modified: 2006-07-02 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marcin Krzyzanowski 2005-01-11 10:45:48 UTC 
Steps to reproduce:
1. build gnome-network-1.99.2
2. run gnome-netinfo


Stack trace:
3. I get:
*** glibc detected *** free(): invalid pointer: 0xbfffd390 ***
Program received signal SIGABRT, Aborted.

in file:
 gnome-netinfo/info.c:info_get_interfaces ()
comment out line:
 items = g_list_append (items, iface);

will stop crash.



Other information:
I think it can be a glib realted bug because I don't see a problem in sources
with this list.
Comment 1 Marcin Krzyzanowski 2005-01-11 11:14:36 UTC 
--- gnome-netinfo/info.c.orig   2005-01-11 12:08:47.303514088 +0100
+++ gnome-netinfo/info.c        2005-01-11 12:09:06.617577904 +0100
@@ -322,7 +322,7 @@
                        break;
                }
        }
-       g_free (ifr);
+/*     g_free (ifr); */
 }

 GList *
Comment 2 Owen Taylor 2005-01-14 18:04:22 UTC 
Almost completely positively a gnome-netinfo bug ... (it might
be corrupting memory elsewhere). GList is really heavily tested
code.
Comment 3 Germán Poo-Caamaño 2005-12-21 18:45:38 UTC 
MAy you try again using gnome-nettool? gnome-network is not being developed anymore and gnome-netinfo.c is info.c in gnome-nettool.
Comment 4 Olav Vitters 2006-07-02 13:05:01 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!