RE: Core dump during CVS Commit

Hi Dreek, Thanks for the mail. Could you update me how shall I take stack trace from core? Thanks Smruti -Original Message- From: Derek Price [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 5:55 PM To: Smruti Cc: bug-cvs@gnu.org Subject: Re: Core dump during CVS Commit

Re: OpenBSD 3.6 sparc64 Build Failure on TRUNK

Derek One of the things it does is verify that the requested executable Derek exists and that it is a GNU application. This is what caught us - the Derek script was assuming that any GNU program is good and therefore that Derek its failure meant a real failure. I added a new bison

Re: Core dump during CVS Commit

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