arts bugs

[George Staikos]

On July 4, 2003 15:08, Stefan Westerfeld wrote:

> I think you're seeing the representation of a "null pointer" here. Calling
> a method on a "null pointer" is expected to segfault (as would calling a
> method on an ordinary C++ object which is NULL). Code which gets object
> references from somewhere should call foo.isNull() prior to calling any
> methods on foo, to ensure that no segfaults occur.
>
> I can not reproduce a crash here, though. I can properly load an example
> and execute it. I know that there is a problem if you have compiled
> artsbuilder with some gcc versions
> (http://bugs.kde.org/show_bug.cgi?id=51667)... maybe you can make a
> backtrace of artsbuilder and see if artsd crashes, too (then make a
> backtrace of artsd as well)?

   I'm using gcc 2.95.x.  Valgrind shows lots of badness happening.  When I 
get a chance I'll have to regenerate all the information I had.

  More important right now is the artsdsp corruption, though I suspect that 
much of it is related.  artsdsp is doing really bad things for a large number 
of users.  Also the getpwuid() patch seems to be really triggering problems.  
For some reason getpwuid_r() doesn't help though, so it's not threading 
problems at that point anyways.

-- 
George Staikos
KDE Developer			http://www.kde.org/
Staikos Computing Services Inc.	http://www.staikos.net/