What's up with /lib/tls/i686/cmov/libthread_db.so.1 ?

[Simon Rönnqvist]

On Saturday 25 February 2006 21:47, Derek Broughton wrote:
> Simon Rönnqvist wrote:
> > (no debugging symbols found)
> > Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> > (no debugging symbols found)
> > `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
> > (no debugging symbols found)
> > (no debugging symbols found)
> > (no debugging symbols found)
> > (no debugging symbols found)
> > (no debugging symbols found)
> > (no debugging symbols found)
> > (no debugging symbols found)
> > ...
> > ...
> > ...
> >
> > What's up with this?
>
> Probably nothing - at least not in libthread.  There'll be a whole lot more
> libraries and information further (likely, much further) down the
> traceback, and it's probably one of those that's the problem.
> --
> derek


OK... the report tends to end with something about libc.so.6, ie.
#210 0xb7d6b391 in malloc () from /lib/tls/i686/cmov/libc.so.6

I don't know what to do... file a bugreport each time this happends? The 
problem is that these crashes are seldom reproducable, because I usually 
don't know what causes them... they just happend every now and then in 
different apps. This is probably not just my problem since I've been having 
this problem in both Hoary and Breezy and on different platforms. If this is 
not something happening to everyone, then it has to be something with my 
home-directory which I've been copying along when changing computer.

If this is a common problem, which I assume it is... then I'm wondering when 
will it end? With Dapper? I really love Kubuntu and would like to go on using 
it, but as it now seems I'd have to take a break and maybe go for MEPIS 
(since it's the closest to Kubuntu that I could find), while waiting for a 
less flaky Kubuntu.

  cheers, Simon