To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=83545
------- Additional comments from [EMAIL PROTECTED] Fri Jan 25 11:16:34 +0000 2008 ------- I did see something with the inbuilt 3.6 icu after it exited. A valgrind warning about a pointer being freed. But no bt details. Using 3.8 icu and there was no such warning. Playing with the icu examples, I saw that the same warning appeared in the simple "break" example if I manually hacked out explicitly linking to libicudata and it disappeared on restoring it. i.e. valgrind ./break ==16516== Invalid free() / delete / delete[] ==16516== at 0x4A0560B: free (vg_replace_malloc.c:233) ==16516== by 0x36CC31043A: free_mem (dl-libc.c:235) ==16516== by 0x36CC30FFC9: __libc_freeres (set-freeres.c:47) ==16516== by 0x4802344: _vgnU_freeres (vg_preloaded.c:60) ==16516== by 0x36CC23513A: exit (exit.c:90) ==16516== by 0x36CC21E2BA: (below main) (libc-start.c:252) ==16516== Address 0x4F50870 is not stack'd, malloc'd or (recently) free'd As libicuuc links to libicudata anyway it would suggest a link ordering problem if libicuuc is not followed immediately by libicudata in a command line app. --------------------------------------------------------------------- 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]
