Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Using a DISPLAY pointing to a Mac OS X machine with XFree4.2 over ssh, makes soffice coredump at start up | ||
---|---|---|---|
Product: | ui | Reporter: | ravn <ravn> |
Component: | code | Assignee: | christof.pintaske |
Status: | CLOSED DUPLICATE | QA Contact: | issues@ui <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | OOo 1.0.0 | ||
Target Milestone: | --- | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
ravn
2002-06-06 09:42:05 UTC
OS->CP: Can you help out here? I really think this one is duplicate to issue 4395. It would be great if you could provide a complete stacktrace to that issue. *** This issue has been marked as a duplicate of 4395 *** The stacktrace did not provide any useful information since the binary did not contain debug info. If you start providing builds with debug-info (sorry, I do not have time to set up the complete compiling environment on this machine) I will be happy to provide whatever you need. Is there a good description on how to run soffice inside gdb? The shell script wrapper does not exactly make it easy. usually I hacke the soffice script. I exchange the very last exec "$sd_prog/$sd_binary" "$1" "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9" with gdb "$sd_prog/$sd_binary" That starts the gdb in the desired environment. In gdb I just say run. I don't need debug information (though it would be fine). Im interested in a callstack. As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. |