Re: big orbit problem.

On Thu, 11 Nov 1999 wrote:
> CORBA_string_dup is somehow doing something to the memory around it.
> *argc before is 1 like it should be, and
> after, argc is NULL. This is bad. Very BAD.
> It is odd that it doesnt segfault the program flat out.
> This is not the first time I have seen CORBA_string_dup do this.

It isn't CORBA_string_dup, and it's not odd that the program doesn't
segfault. What you have here is random memory corruption; it happens to
write over argc. Because argc is valid memory, you get no segfault.

So, you need to find what part of your program is screwing up memory it
isn't supposed to touch.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]