Yeah, I stayed up on Cooker on a semi-daily basis. So all the RPMS are as
uptodate as Cooker is. I've had two other crashes today, one from Konqueror
and one from KNode, with almost identical backtraces.
Robby
On Friday 13 July 2001 07:38 am, Jose M. Sanchez wrote:
> Out of curiosity did you perform the updates?
>
> I received a lot of crashes only after performing the updates. I ended
> up going back to the stock installation and the crashes went away.
>
> -JMS
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
> Behalf Of Robby Stephenson
> Sent: Wednesday, July 11, 2001 5:41 AM
> To: [EMAIL PROTECTED]
> Subject: [expert] random crashes in libc
>
>
> Hi,
>
> I've gotten a couple random crashes, unreproducable, in the last few
> days,
> mostly within KDE applications, and the debug output is shown below.
> From
> what little I know, not helpful at all.
>
> [New Thread 1024 (LWP 29641)]
> 0x41226859 in wait4 () from /lib/libc.so.6
> #0 0x41226859 in wait4 () from /lib/libc.so.6
> #1 0x412996a4 in __check_rhosts_file () from /lib/libc.so.6
> #2 0x409b213e in KCrash::defaultCrashHandler (signal=0) at
> kcrash.cpp:197 #3 0x41139ce7 in _IO_2_1_stderr_ () from
> /usr/lib/libstdc++-libc6.2-2.so.3
>
> This particular one is a KMail crash, from KDE2.2beta1, current Cooker
> RPMS,
> which happened on a "Check for New Mail" operation. Is this a bug in
> libc,
> glibc or something connected? Is it worth reporting anywhere? More
> importantly, is there anyway to be able to tell how to reproduce it?
>
> Thanks,
> Robby
