We did more investigation last
night. This isn’t a problem from other UNIX boxes and it’s not
a problem from Eclipse. The only time a core file is created is a result
of using WinCVS / CVSNT clients to connect to the repository. Connections
and communications are done using pserver. I even went back to WinCVS 1.3
and used the client from that version (which was available at the same time we
built 1.11.5 of the repository). That didn’t work either.
Here’s a trace:
CVSROOT: address@hidden:/source/CVS
(password authentication)
cvs login
Logging in to
:pserver:address@hidden:2401:/source/CVS
***** CVS exited normally
with code 0 *****
cvs watch add (in directory C:\PROJECTS\java\eclipse\myproject\)
? web/images/_new_ logo.gif
***** CVS exited normally
with code 0 *****
cvs update -C (in directory C:\PROJECTS\java\eclipse\myproject\)
? web/images/_new_ht_logo.gif
cvs server: Updating .
cvs server: Updating bin
cvs server: Updating conf
cvs server: Updating conf/dev
cvs server: Updating conf/prod
cvs server: Updating lib
cvs server: Updating sql
cvs server: Updating src
cvs server: Updating web
cvs server: Updating web/css
cvs server: Updating web/images
U web/images/logo.gif
U web/images/up_arrow.gif
***** CVS exited normally with code 0 *****
I read another post from someone that was
having similar problems on an AIX box. Their cores were resulting from
segmentation faults. I had someone open up the core with a debugger and
it basically looks like CVS can’t clean up after itself as it should.
The debugger had some messages about segmentation faults as well. The
patch that I saw for this problem in the archive basically just prevents the
core file from being written.
We actually had this problem when we first
started using WinCVS over a year ago, but we quickly abandoned the use in favor
of using Eclipse. Now that we’re moving to JDeveloper, we have to
use the client that’s installed on our local machines. As a result
we now have a high dependency on CVSNT / WinCVS. We’re considering
trying to move the repository to a Suse box and get off the AIX box altogether,
but that’s a project in and of itself with no guarantees.
Thanks,
Derek
From: Arthur Barrett
[mailto:address@hidden
Sent: Wednesday, November 16, 2005
8:15 PM
To: Derek Nerenberg;
address@hidden
Subject: RE: CVS Core on AIX
You seem to have forgotten to include a
trace.
Without the trace we can't see important
information such as the CVSROOT that you are using, protocol etc. Does
the same command (using exactly the same CVSROOT, including protocol and
network address) work ok on the server? If you are using SSH ensure that
the CVS_SERVER variable is set correctly on the client.
2.0.51d is getting pretty old now - but
should never cause a crash on the server.
-----Original Message-----
From: Derek Nerenberg
[mailto:address@hidden
Sent: 17 November 2005 00:15
To: Arthur Barrett;
address@hidden
Subject: RE: CVS Core on AIX
I just downloaded the client which is the 2.0.51d version.
When I try to login using command line options without JDeveloper even started,
it cores out on the CVS server. I suspect there are problems with the
versions. I’d like to download the correct client for a repository
that’s 1.11.5 version, but can’t seem to figure out how / where to
get the correct client. Any assistance would be greatly appreciated
Thanks,
Derek
From: Arthur Barrett
[mailto:address@hidden
Sent: Wednesday, November 16, 2005
3:35 PM
To: Derek Nerenberg; address@hidden
Subject: RE: CVS Core on AIX
The first step in debugging what is going on is to get a trace:
Try and rule out the JDeveloper GUI by using the command line for
your tests instead, and give a specific example of something that causes a
crash (ie: "everything" is not specific - does "cvs
version" cause the crash? What about "cvs login"? etc
For info on how to debug AIX core files you should probably ask
either the GCC or AIX newsgroups...
-----Original
Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of Derek Nerenberg
Sent: 16 November 2005 16:52
To: address@hidden
Subject: CVS Core on AIX
Hello,
I’m
having a problem using the newest version of CVSNT client (via
JDeveloper). Everything I do through the JDeveloper GUI will generate
core files in /tmp. CVS 1.11.5 is running on AIX 5.
I do not
have admin privileges on the CVS repository, but am tasked with figuring this
out. Can someone give me some instructions on using the debugger so I can
interpret the cores for you?
Kind
Regards,
Derek