On Mon, 25 Nov 2002, Net Llama! wrote:
On Tue, 19 Nov 2002, Jim Bonnet wrote:
Or.. Have you run a debugger against the programs to see if you can find
the actual line of code that is causing the fault? Maybe its a lib call
and you can pinpoint the lib that way.
I don't even have
On 11/25/2002 11:42 AM, someone claiming to be Net Llama! wrote:
On Mon, 25 Nov 2002, Net Llama! wrote:
snip
Does this mean that the problem is with /lib/libpthread.so.0 ?
I think i've figured out (part of) thje problem. Somehow, and i've yet to
figure out how, when i was attempting to
On Mon, 25 Nov 2002, Tim Wunder wrote:
On 11/25/2002 11:42 AM, someone claiming to be Net Llama! wrote:
On Mon, 25 Nov 2002, Net Llama! wrote:
snip
Does this mean that the problem is with /lib/libpthread.so.0 ?
I think i've figured out (part of) thje problem. Somehow, and i've yet
On Mon, 25 Nov 2002, Kurt Wall wrote:
On Mon, Nov 25, 2002 at 11:42:35AM -0500, Net Llama! wrote:
Does this mean that the problem is with /lib/libpthread.so.0 ?
Possibly.
Nope, turned out to be the symlink:
/lib/libc.so.6 - /lib/libc-2.2.5.so
I still can't figure out how that got set
On 11/25/2002 2:05 PM, someone claiming to be Net Llama! wrote:
On Mon, 25 Nov 2002, Tim Wunder wrote:
snip
Actually i've upgraded to glibc-2.2.5 on 3 of my boxes in teh past 2
weeks. This is the only one that blewup.
My recomendation? Punt.
Assuming your data is backed up. Reinstall the
