Not a compiler problem then, let's shoot for memory-handling problems. They can be easily found using Valgrind, and are a mess to track down otherwise:
* Build unoptimized and with debug metadata to improve stack traces: make clean ; make CFLAGS="-O0 -g" * Install Valgrind if you don't have it already: sudo apt-get install valgrind * Remove bubblemon from any panel. * Launch bubblemon in valgrind: valgrind ./src/bubblemon-gnome2 * Wait for 20 seconds. This step is really important. When running inside Valgrind, bubblemon needs some time to start up. The only way to notice if this step is done is to have another system load meter, and when it goes back down to 0, you can go on to the next step. Nothing will appear on any panel until the next step. Unless you wait long enough, another bubblemon will be started outside of Valgrind. * Add bubblemon to a panel somewhere. You'll notice that it's running inside Valgrind by that it's really slow to start up. It seems like Valgrind JITs things at least on IA32, since for me showing the tooltip or the menu for the first time are really slow, but then get a lot faster. * After bubblemon crashes, please send me all output you have in the terminal window. Hopefully Valgrind will provide one or more stack traces helping track down the source of the error. If you get stack traces with lots of ??s in them, you might need to install the gnome-dbg and libc6-dbg packages to be able to get proper stack traces through GNOME and libc code. If this doesn't help, *then* we'll have to start looking at instrumented builds. Regards //Johan 2009/1/8 Jean-Luc Coulon (f5ibh) <jean-luc.cou...@wanadoo.fr>: >>make clean ; make CFLAGS=-O0 && sudo make install > > I rebuilt bubbleon this way… and it crashed after a couple of hours. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
