Re: Analysing core files

From: grid (prohit99_at_gmail.com)
Date: 11/25/05 

Date: Fri, 25 Nov 2005 11:18:39 +0530

Paul Pluzhnikov wrote:
> grid <prohit99@gmail.com> writes:
>
>>I have a long running program so its difficult to attach to the
>>program
>
> Why? How long the program runs has absolutely nothing to do with
> attaching a debugger to it.

I have a server that always running,and we have clients that connect to
the server.For every client connection we do a fork.So there is one
forked process thats told to do something and it dosent do well.There
will be multiple connections one after the other and each connection
does its little task and exits.Now its difficult for me to track which
is the one failing and to attach to it in a debugger.

>>I was thinking if I can make use of some the details present in the
>>core file which the debugger dosent inform.
>
> There are details in the core file which an expert might be able
> to extract. Unfortunately, you'll need to observe the expert doing
> it to find out how it's done :)
I know it requires an expert and I am none and that brings me here.Maybe
you guys can give me some pointers which can be helpful.

Regarding the Linux Vs Solaris thing,this works on Solaris but fails in
IA64 Linux.But I need it to be working on Linux,there are no
alternatives.Because I know it might be a OS specific thingy,thats
probably not properly implemented on this platform in Linux.One of the
strings in the core file says :

internal error: symidx out of range of fptr table
cannot map pages for fptr table
cannot map pages for fdesc table

Thanks,
~

Relevant Pages