| Summary: | unopkg gui crashes during exit | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Gökçen Eraslan <gokcen.eraslan> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bfo.bugmail, lo_bugs, reisi007 |
| Priority: | medium | ||
| Version: | 3.4.1 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | GDB trace file | ||
|
Description
Gökçen Eraslan
2011-07-11 04:02:19 UTC
Also when I try to print m_pSolarMutex: (gdb) p m_pSolarMutex Cannot access memory at address 0x28 we don't have currently the easy valgrind stuff in unopkg, so if you want to valgrind this to get even more info then.
export G_SLICE=always-malloc
and
edit the unopkg script to change
exec "$sd_prog/unopkg.bin" "$@" "$JVMFWKPARAMS" \
"-env:INIFILENAME=vnd.sun.star.pathname:$sd_prog/redirectrc"
to
valgrind --num-callers=50 "$sd_prog/unopkg.bin" "$@" "$JVMFWKPARAMS" \
"-env:INIFILENAME=vnd.sun.star.pathname:$sd_prog/redirectrc"
and let that rip (ever so slowly) and attach the output of that.
to reproduce this, is it necessary to actually install or do anything with the unopkg gui ? or is it just open it and then try and close it ?
I am working on ubuntu natty from master commit id 5052b81, and my
autogen.lastrun says ...
--disable-mozilla
--enable-symbols
--enable-dbgutil
--enable-crashdump
--disable-build-mozilla
--without-junit
Before the segmentation fault the program twice issues the message ...
Error: object deleted while in use ! From File /home/terry/lo_hacking/git/libo/vcl/inc/svdata.hxx at Line 438
HTH. If not, I apolgize for the noise.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Still reproducable in 3.5.5.3 / Fedora 17. (In reply to comment #9) > Still reproducable in 3.5.5.3 / Fedora 17. Could you please recheck on latest active branch (4.1.4)? Seems fixed in 4.1.3 RESOLVED WORKSFORME per comment 11. |