Re: ost::String class release 1.1.1

[David Sugar]

Hmm...

text is either assigned from a slot list (linked list) or from mempager 
alloc'd memory.  If the linked list is messed up, that is one possibility.  
However, the other option is if the string is too large, a simple new is 
used, and text is never modified.  Text is not initialized because it does 
not need a value until it needs to be assigned from the list or from 
mempager.  Hence, it would help to know more about where precisely this 
segfault occurs.  One thing you can do is initially set text to NULL at the 
start of getSpace, as that would make it easier to determine what the real 
state of text is at the time it happens; whether its before or after it has 
been assigned by something.

On Monday 05 April 2004 12:15 pm, address@hidden wrote:
> Everyone,
>       I'm noticing instances of seg faults in the ost::String::getSpace()
> method, where the *text variable is assigned what appears to be random
> garbage, and is yet used as a pointer into some data structure.
>
>       Has anyone else experienced a similar failure?
>
>       Is there a patch to the ost::String class that needs to be applied?
>
>       Thanks,
>               Erik.
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp