To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94659 Issue #|94659 Summary|Assertion failed: sal/rtl/source/alloc_cache.c:926 Component|porting Version|DEV300m31 Platform|Opteron/x86_64 URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|mhu Reported by|mhu
------- Additional comments from [EMAIL PROTECTED] Mon Oct 6 10:33:53 +0000 2008 ------- As posted to [EMAIL PROTECTED] -------- Original Message -------- Subject: [dev] OSL_ASSERTs in rtl_cache_create() Date: Tue, 23 Sep 2008 12:42:19 +0200 From: David Tardon <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi, can someone explain to me (and anyone else interested) reason for OSL_ASSERT's in sal/rtl/source/alloc_cache.c at lines 925 and 926 (DEV300_m31)? Their presence disables OOo to compile with --enable-dbgutil on x86_64. The problem is that on x86_64 during initialization of gp_cache_arena in rtl_cache_once_init(), rtl_arena_activate() calls rtl_cache_create(), which calls rtl_cache_activate(). Now, at line 924, cache->m_slab_size is calculated to be 8192 on x86_64, so it takes the 'if' branch (on i386 it takes the 'else' branch, where there is no OSL_ASSERT present; so no problem) and ends here, because gp_cache_slab_cache and gp_cache_bufctl_cache haven't been initialized yet. As gp_cache_arena is used during _their_ initialization, it's not possible to simply move initialization blocks in rtl_cache_once_init(). David --------------------------------------------------------------------- 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]
