To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51560
------- Additional comments from [EMAIL PROTECTED] Thu Jan 5 16:21:58 -0800 2006 ------- Yes, I forgot to tell you that the cores are called *.stackdump :) First I would go to the latest snapshot. Debugging old snapshots is, most of the time, only of limited interest to the developer. Then I would start shortening the configure script until only the failing part remains. As you didn't post any output after the configure call I would assume that something at the beginning fails. Have a look at config.log. For making bash scripts more verbose look at "man bash" (sh == bash). But in this case this might not help you as configure is haevily redirecting its output. If you would have a bash/sh with debug information you could use addr2line to get the failing position in the code (but you don't). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
