On 18/06/2010 12:08, Davide Dozza wrote:
> Michael Stahl ha scritto:
>> On 18/06/2010 11:50, Davide Dozza wrote:
>>> I did it.
>> ok,
>>
>>> The problem happens on tstring.cxx
>>>
>>> xub_StrLen ImplStringLen( const sal_Char* pStr )
>>> {
>>> const sal_Char* pTempStr = pStr;
>>> while( *pTempStr )
>>> ++pTempStr;
>>> return (xub_StrLen)(pTempStr-pStr);
>>> }
>>>
>>> *pTempStr is a null pointer.
>>>
>>> Davide
>> well, yes, that's where it crashes.
>> but the problem is that somebody is calling the Len() function on a null
>> pointer.
>> you need to post the stack backtrace to find out where the cause of the
>> problem is.
>> to get the backtrace you need to attach the debugger somehow.
>> (i don't usually work on windows, so i can't remember how that is done...)
>>
>
> I'm not an expert too but is it the call stack?
> It's enough if I just cut and paste info in it?
>
> Davide
did you attach something to your mail?
because i'm wondering what "it" is, and the most likely explanation is
that "it" is an attachment that the silly mailing list software has
removed from your mail.
please paste "it" into your mail instead :)
--
Why does New Jersey have more toxic waste dumps and California
have more lawyers? - New Jersey had first choice.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
