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 172792 - panel and gnome-menu-spec-test crash
panel and gnome-menu-spec-test crash
Status: RESOLVED FIXED
Product: gnome-menus
Classification: Core
Component: libgnome-menu
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-menus dummy account
gnome-menus dummy account
: 172793 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-04-06 11:37 UTC by Diego González
Modified: 2005-04-08 11:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
the output of gnome-menu-spec-test (12.53 KB, application/octet-stream)
2005-04-06 23:26 UTC, Diego González
Details
the directory causing the crash and its contents (4.02 KB, application/x-compressed-tar)
2005-04-07 08:22 UTC, Diego González
Details

Description Diego González 2005-04-06 11:37:38 UTC
this is the backtrace it get when running gnome-menu-spec-test:

the backtrace consists of calls like this, more than a thousand as you can see

  • #1100 process_only_unallocated
    at menu-tree.c line 3171

I'm using gnome-menus from today CVS HEAD
Comment 1 Mark McLoughlin 2005-04-06 12:35:49 UTC
*** Bug 172793 has been marked as a duplicate of this bug. ***
Comment 2 Mark McLoughlin 2005-04-06 12:41:48 UTC
Not seeing this here, so could you attach

  1) the output of MENU_VERBOSE=1 gnome-menu-spec-test

  2) the full backtrace

  3) the contents of the menu files loaded - search for "from disk" in
     the log file in (1)

Also, was this just introduced by recent changes to HEAD or could you see the
problem before?
Comment 3 Diego González 2005-04-06 23:25:50 UTC
ok, here we go: 

1) attached
2) impossible, i don't know how to get it, i put a static variable into the
recursive function that causes the crash, it is reentered more than two million
times before crashing.
3) attached

i don't know when it was introduced was it is being quite long since i last
compiled this module.
Comment 4 Diego González 2005-04-06 23:26:38 UTC
Created attachment 39776 [details]
the output of gnome-menu-spec-test
Comment 5 Mark McLoughlin 2005-04-07 07:12:38 UTC
Thanks, unfortunately I can't see anything strange in (1) 

Wrt. to (2) why not just pipe the output of gdb to a file ? One thing I'd like
to find out is whether the same directory is being passed to each frame or if
there's any pattern, so even pasting a few more frames will help.

You forgot to attach (3)

Comment 6 Mark McLoughlin 2005-04-07 07:13:22 UTC
Btw, it might be worth trying to do a completely clean build from CVS - it could
have been a miscompile of some sort
Comment 7 Mark McLoughlin 2005-04-07 07:14:44 UTC
Perhaps also try

valgrind --tool=memcheck --leak-check=yes --show-reachable --num-callers=15
gnome-menu-spec-test

too
Comment 8 Diego González 2005-04-07 08:21:24 UTC
oh sorry, it was very late. Here is the information and even more:

*) the same direcrtory is passed over and over the pointers are always the same.

*) I found the culprit, it is the directory /usr/share/applnk attached are the
contents of that directory. Removing them fixes the segfault in both
gnome-menu-spec-test and gnome-panel.



Comment 9 Diego González 2005-04-07 08:22:05 UTC
Created attachment 39791 [details]
the directory causing the crash and its contents
Comment 10 Mark McLoughlin 2005-04-07 08:52:28 UTC
Thanks, very helpful. Try CVS HEAD again now:

2005-04-07  Mark McLoughlin  <mark@skynet.ie>

        Hopefully fixes crash in bug #172792.

        * libmenu/menu-tree.c: (menu_tree_item_unref): don't unref the
        parent because we don't hold a ref on it anymore.

Comment 11 Diego González 2005-04-08 11:15:47 UTC
it's fixed, thanks a lot.

Awesome work you're doing, by the way.