[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: assertion fault. on loggin
From: |
Paul Edwards |
Subject: |
Re: assertion fault. on loggin |
Date: |
Mon, 25 Aug 2003 21:48:29 GMT |
"Pierre" <pceteaudatmacif.fr@netcourrier.com> wrote in message
b86193eb.0308250158.34715117@posting.google.com">news:b86193eb.0308250158.34715117@posting.google.com...
> Paul writes :
> > Well, those look like very unusual addresses to me.
> >
> > But fn looks more reasonable.
> >
> > Can you try putting
> > > if (fstat ( (fn = fileno (bc->fp)), &s ) != -1)
> >
> > instead of == -1
> >
> > so that I can see what good pointer values look like on your system.
>
> On a login :
> bc is 2002f7d8
> bc->fp is f0004c00
> fn is 3
Ok, so the pointers are actually reasonable after all, the problem
would appear to be the file number.
> >Did you get a core dump? Can you examine it with a debugger and get a
> >traceback?
> Yes, we get a core dump.
> We are looking for a way to get the traceback ( a bit technical, isn't-it ?
> ;) )
Make sure you get the core dump from the first one, ie with "== -1".
Although I suspect that given that the pointers look reasonable,
we're not going to be able to tell anything from the coredump,
it will instead need judicious use of
printf("fn is %d\n", fileno(bc->fp)) at various spots in order to
find the culprit.
Try to keep this a controlled experiment by only dealing with
"cvs login".
We'll wait for the original core dump before looking for that.
BFN. Paul.