[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core dump during CVS Commit

From: Derek Price
Subject: Re: Core dump during CVS Commit
Date: Thu, 16 Jun 2005 09:54:55 -0400
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Smruti wrote:

>Hi Dreek,
>Thanks for the mail.
>Could you update me how shall I take stack trace from core?

Using the GNU debugger (gdb), the command is `bt' (for "backtrace"). 
Thus, assuming that you were using /usr/bin/cvs and that your core dump
created a file named "core.1234" (where "1234" couild be any process id):

$ gdb /usr/bin/cvs core.1234
...assorted gdb bootup output...
(gdb) bt

The commands may be slightly different if you need to use the Solaris

The core dump file should have been created in whatever directory you
ran the offending CVS command from.  If it wasn't, you might have to run
the command `ulimit -c unlimited' to enable core dumps.  At least,
that's the command on Linux - I'm not sure that is the same on Solaris



reply via email to

[Prev in Thread] Current Thread [Next in Thread]