To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=65788
------- Additional comments from [EMAIL PROTECTED] Sun Jun 11 20:23:58 -0700
2006 -------
I did some tracing in idlc and have the following observations
(a) Bus Error occurs sometimes, but only when trying to execute this command in
idlc/source/idlcproduce.cxx
// produce registry file
if ( !idlc()->getRoot()->dump(rootKey) )
Further testing shows that idlc()->getRoot() is OK but an error occurs in
dump(rootKey).
(b) dump(rootKey) is implemented in idlc/source/astdeclaration.cxx at row 172
function
sal_Bool AstDeclaration::dump(RegistryKey& rKey)
(c) This function is recursive by including the following statement in a while
loop:
bRet = pDecl->dump(rKey);
(d) Tryin g to understand what dump does, it appears the rKey has a variable
number of members and the getRoot checks if the last member is included in a
list of known types such as NT_module.
(e) With normal operation the function is re-entered 5 times, the first 4 times
finding type NT_module and the 5th time finding a different type. After the 5th
re-entry then the while loop is completed and the dump function returns 5 times.
(f) In failure operation the function enters 5 times and identifies the 5th type
but never returns, as the Bus Error occurs at that point.
(g) The first Bus Error is noted with type NT_enum, and if that is bypassed as
described in earlier comments, then the error occurs next with NT_struct.
I will attach a log of running udkapi and the patches to idlc that print out
that log.
>From reading about recursion it appears a useful test would be to implement
>dump
with some kind of loop so it is not recursive but I have no idea yet how to do
that.
I have not figured how to run this with gdb yet, I can see that idlccpp is
called by execv from sal.
This is very slow work for me, and as it works with alignment 8, I wonder if it
is worth any more work at all?
---------------------------------------------------------------------
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]
