To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92638


User fs changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Wed Sep 10 12:29:53 +0000 
2008 -------
Ah ...

There was a detail in the stacks which slipped my attention. In fact the crash
is not where I though it is (PrepatedStatement::setBinaryStream in dbaccess),
but in the the JVM, which was called with heavily invalid parameters by our JDBC
bridge (PreparedStatement in connectivity).

The root cause here is the problem discussed recently in our mailing list: In
fact, the implementation of setBinaryStream assumed that length was the number
of available bytes in the stream. Because of the above-mentioned bug in the
Basic script, there were actually *0* bytes available in the stream, but this
was ignored by the implementation - it passed a memory location at which *0*
bytes were stored to the JVM, also telling it that it could expect *nLength*
bytes there.

This in fact perfectly fits to the observations that the script crashes
sometimes only - this is a typical result of such bad-memory-access bugs.

I committed a fix to CWS dba31c. Even if I could not reproduce the concrete
crash, I'm pretty confident it's fixed then.

---------------------------------------------------------------------
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]

Reply via email to