Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RE: Debugger Doesn't Show Program Lines

0 views
Skip to first unread message

Nelson R Pardee

unread,
May 4, 2007, 10:17:28 AM5/4/07
to debu...@perl.org
I found that the combination of -w -d didn't work. But if I did "use
warnings" with -d, the problem went away. I don't think that's what's
supposed to happen, but it's a usable workaround. And 5.8.x had the same
problem, I believe.

> -----Original Message-----
> From: Richard Foley [mailto:Richar...@rfi.net]
> Sent: Friday, May 04, 2007 08:25
> To: debu...@perl.org
> Cc: Nelson R Pardee
> Subject: re: Debugger Doesn't Show Program Lines
>
> Perhaps it's a problem with 5.6.1, have you tried a more
> recent version of Perl, like 5.8.n?
>
> --
> Richard Foley
>
> > In-ReplyTo: Pine.SOL.4.51.07...@gamera.syr.edu
> >
> > We're upgrading from an old 5.005_03 to v5.6.1. Now when I
> use -d on
> > via the first line of the program, it starts in debug mode but no
> > lines of the program are visible & they are unlistable.
> If I do an
> > R, then they
> are
> > visible. <Perl -d pgmname> doesn't have this problem.
> >
> > We're also running into problems reading stdin, and nntp complains
> > about Can't call method "post" on an undefined
> value at eg.pl line 1607.
> The
> > script runs fine under the old version of perl.

Nelson R Pardee

unread,
May 4, 2007, 11:10:52 AM5/4/07
to debu...@perl.org
I don't even know how to file a bug report, and right now this problem
is "ages" ago in terms of projects:-)

> -----Original Message-----
> From: Richard Foley [mailto:Richar...@rfi.net]
> Sent: Friday, May 04, 2007 11:14
> To: debu...@perl.org
> Cc: Nelson R Pardee

> Subject: Re: Debugger Doesn't Show Program Lines


>
> On Friday 04 May 2007 16:17, Nelson R Pardee wrote:
> > I found that the combination of -w -d didn't work. But if I
> did "use
> > warnings" with -d, the problem went away. I don't think
> that's what's
> > supposed to happen, but it's a usable workaround. And 5.8.x had the
> > same problem, I believe.
> >

> Spooky.
>
> Have you filed a bug report yet?
>
> --
> Richard Foley
> Ciao - shorter than aufwiedersehen
>
> http://www.rfi.net/
>
> ps. Please resend any bounced or unanswered emails.
>

Richard Foley

unread,
May 4, 2007, 11:14:22 AM5/4/07
to debu...@perl.org, Nelson R Pardee
On Friday 04 May 2007 16:17, Nelson R Pardee wrote:
> I found that the combination of -w -d didn't work. But if I did "use
> warnings" with -d, the problem went away. I don't think that's what's
> supposed to happen, but it's a usable workaround. And 5.8.x had the same
> problem, I believe.
>

Richard Foley

unread,
May 4, 2007, 8:24:50 AM5/4/07
to debu...@perl.org, nrpa...@syr.edu
Perhaps it's a problem with 5.6.1, have you tried a more recent version of
Perl, like 5.8.n?

--

Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

ps. Please resend any bounced or unanswered emails.

> In-ReplyTo: Pine.SOL.4.51.07...@gamera.syr.edu


>
> We're upgrading from an old 5.005_03 to v5.6.1. Now when I use -d on
> via the first line of the program, it starts in debug mode but no lines of
> the program are visible & they are unlistable. If I do an R, then they
are
> visible. <Perl -d pgmname> doesn't have this problem.
>
> We're also running into problems reading stdin, and nntp complains about
> Can't call method "post" on an undefined value at eg.pl line 1607.
The
> script runs fine under the old version of perl.
>

> Thanks in advance for help.
>
> Nelson
>
> --Nelson R. Pardee, Support Analyst, Information Technology &
Services--
> --Syracuse University, CST 4-191, Syracuse, NY 13244 --
> --(315) 443-1079 [EMAIL PROTECTED] --

Richard Foley

unread,
May 4, 2007, 11:31:47 AM5/4/07
to debu...@perl.org
On Friday 04 May 2007 17:10, Nelson R Pardee wrote:
> I don't even know how to file a bug report, and right now this problem
> is "ages" ago in terms of projects:-)
>
Well, for the next one, just run perlbug :-)
0 new messages