After a long time and a difficult task (at least for me) I had the dbgsym installed. Then I run valgrind. Please, see comment #7: when I run gnome-help "inside" valgrind the bug disappear, I mean gnome-help won't crash while printing (please, remember that the bug actually was a crash when printing, always for each printing command - I never had a page printed ...).
The situation is the same as some days ago: gnome-help alone crashes gnome-help with gdb crashes gnome-help with valgrind doesn't crash - so no bug report with valgrind is generated However, now I generated a new crash report with gdb. No file was generated into /var/crash and therefore I'm not able to follow Your instructions this way. I'm attaching the new logfile from GDB which seems to be full of debugging symbols. Is this enough or should I do something more? Thanks so far. Ciao CM ** Attachment added: "GDB log output (TXT) with debugging symbols" http://launchpadlibrarian.net/50909309/gnome-help-crash.txt -- gnome-help crashed (segmentation fault) while printing https://bugs.launchpad.net/bugs/580206 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
