Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!charyb!dan
From: dan@kfw.COM (Dan Mick)
Newsgroups: comp.lang.perl
Subject: Re: perl 3.0 pl 12
Summary: news about perl -d dumping core
Message-ID: <1990Mar8.021513.8913@kfw.COM>
Date: 8 Mar 90 02:15:13 GMT
References: <1990Mar7.032442.2312@kfw.COM>
Reply-To: uunet!charyb!dan (Dan Mick)
Organization: KFW Corporation, Newbury Park, CA
Lines: 20

I've discovered that it's almost always the case that cmd->c_next is null
at that point (line 78 in cons.c), as cons.c:75 calls make_ccmd(), which 
calls dodb(), which calls append_line(), which looks like it adds to the
end of the list without setting c_next.  I don't know whether or not 
c_next should be set to the head of the list or what, but if I change
line 77 in cons.c from

if (perldb)

to

if (perldb && cmd->c_next)

I can actually get into the debugger.

The odd thing is, it seems this happens on *any* perl script that has a
return in a subroutine...it doesn't seem to be affected by machine-dependent
options.

Larry?