OK. Here's what I get from dbx:
$ dbx /usr/local/bin/cvs core
Type 'help' for help.
reading symbolic information ...
[using memory image in core]
Segmentation fault in expand_catname at 0xd01895b0 ($t1)
0xd01895b0 (expand_catname+0x18) 9421f780 stwu r1,-2176(r1)
(dbx)
Mark Chojnacki
[EMAIL PROTECTED]
-------------------------------------------
[EMAIL PROTECTED] (Larry Jones)
Sent by: To: [EMAIL
PROTECTED]
info-cvs-bounces+mchojnacki=symcor.c cc: [EMAIL
PROTECTED]
[EMAIL PROTECTED] Subject:
Re: pserver core dumps on WinCVS login
02/26/03 05:08 PM
[EMAIL PROTECTED] writes:
>
> I changed the entry in /etc/inetd.conf to add "-t" to the cvs command
line,
> but I don't seem to be able to find any trace output anywhere. Where
would
> it have been written to?
Trace output goes to stderr, which for a server is probably nowhere,
but it doesn't matter because a trace wouldn't be helpful in this case.
What I meant was, can you use a debugger on one of the core files to get
a traceback?
-Larry Jones
It's hard to be religious when certain people are never
incinerated by bolts of lightning. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
