Pierre CETEAUD writes:
>
> Now, I am waiting for a patch. But I don't see anything coming.
> Perhap's I shouldn't wait and should do something to see this bug fixed ?
>
> I don't have the skill to correct this bug by myself.
> So what should I do ?
http://www.cvshome.org/docs/manual/cvs_23.html
A few days ago I've posted the description of a bug.
People on this mailling list helped me to find the exact causes of this
bug.
I haved post my final analyse of the bug.
Now, I am waiting for a patch. But I don't see anything coming.
Perhap's I shouldn't wait and should do something to see thi
My analyse of the problem was wrong, as I confused *rcsnode and rcsnode
The error was : Assertion failed: *rcsnode == NULL, file
/u/scjones/cvs-nightly/src/commit.c, line 2056
I've got this explanation :
>This assertion failure means that CVS was trying to create a brand new
>RCS file because th
Pierre CETEAUD writes:
>
> 2054 if (rcsnode != NULL)
> 2055 {
> 2056 assert (*rcsnode == NULL);
> 2057 *rcsnode = rcsfile;
> 2058 }
>
> Everyone can see that line 2057 will never be executed. There's something wrong
You're misreading the code. Note that line 20
"Pierre CETEAUD" <[EMAIL PROTECTED]> writes:
> Looking to the code on codecatalog.com I read :
>
> 2054 if (rcsnode != NULL)
> 2055 {
> 2056 assert (*rcsnode == NULL);
> 2057 *rcsnode = rcsfile;
> 2058 }
>
> Everyone can see that line 2057 will never be executed.
The message I got is :
Assertion failed: *rcsnode == NULL, file /u/scjones/cvs-nightly/src/commit.c, line
2056
on a normal commit (I don't know why I got this message in this commit rather than in
another)
Looking to the code on codecatalog.com I read :
2054 if (rcsnode != NULL)
2055
