Re: Help debugging some old Bugzilla perl scripts

On Monday, February 26, 2018 at 4:50 AM, Shlomi Fish" wrote... > Hi jose, > > please see http://www.shlomifish.org/Files/files/code/bugzilla.patch for my > patch against bugzilla 3.2 to get it to compile with recent perls. Thanks. josé -- What if eternity is real? Where will you spend it? H

Re: Help debugging some old Bugzilla perl scripts

Hi jose, please see http://www.shlomifish.org/Files/files/code/bugzilla.patch for my patch against bugzilla 3.2 to get it to compile with recent perls. On Mon, 26 Feb 2018 05:43:45 +0100 "jose cabrera" wrote: > On Sunday, February 25, 2018 at 11:26 PM, "Uri Guttman" wrote... > > > > > > ==

Re: Help debugging some old Bugzilla perl scripts

On 02/25/2018 11:51 PM, jose cabrera wrote: On Sunday, February 25, 2018 at 11:48 PM, "Uri Guttman" wrote... Here is line 1085: foreach my $type qw(dependson blocked) { my @bug_ids = split(/[\s,]+/, $deps_in{$type}); put parens around the qw(). it used to be allowed as the ()

Re: Help debugging some old Bugzilla perl scripts

On Sunday, February 25, 2018 at 11:48 PM, "Uri Guttman" wrote... > >>> Here is line 1085: > >>> foreach my $type qw(dependson blocked) { > >>> my @bug_ids = split(/[\s,]+/, $deps_in{$type}); > >> put parens around the qw(). it used to be allowed as the () in the for > >> loop but no

Re: Help debugging some old Bugzilla perl scripts

On 02/25/2018 11:43 PM, jose cabrera wrote: On Sunday, February 25, 2018 at 11:26 PM, "Uri Guttman" wrote... syntax error at Bugzilla/Bug.pm line 1085, near "$type qw(dependson blocked)" Here is line 1085: foreach my $type qw(dependson blocked) {

Re: Help debugging some old Bugzilla perl scripts

On Sunday, February 25, 2018 at 11:26 PM, "Uri Guttman" wrote... > > > > > > syntax error at Bugzilla/Bug.pm line 1085, near "$type qw(dependson > > blocked)" > > > > Here is line 1085: > > foreach my $type qw(dependson blocked) { > > my @bug

Re: Help debugging some old Bugzilla perl scripts

On 02/25/2018 10:47 PM, jose cabrera wrote: Greetings! Long story, I had to install Bugzilla v3.2, which was in a WinNT 4. I have now installed Bugzilla v3.2, in the Ubuntu 14.04 server, but I have perl (v5.22.1) and I am getting lots of errors. Once I learn to fix one of these, I can work

Help debugging some old Bugzilla perl scripts

Greetings! Long story, I had to install Bugzilla v3.2, which was in a WinNT 4. I have now installed Bugzilla v3.2, in the Ubuntu 14.04 server, but I have perl (v5.22.1) and I am getting lots of errors. Once I learn to fix one of these, I can work with the others. ===

Re: Debugging and passing constant value at run time

LTech" wrote: > I am using constant mainly to enable printing of debugging messages > (e.g. use constant DEBUGGING_L1 => 0;) Normally, the value is '0' and > when I need to see debug messages, I make this 1 and run the script. > > Is there a way to allocate value to

Re: Debugging and passing constant value at run time

On Tue, 7 Jul 2015 11:40:35 + "Sharanbasappa Raghapur, ERS, HCLTech" wrote: > I am using constant mainly to enable printing of debugging messages > (e.g. use constant DEBUGGING_L1 => 0;) Normally, the value is '0' and > when I need to see debug messages,

Re: Debugging and passing constant value at run time

On 07/07/2015 10:52 AM, Ron Bergin wrote: Which means that neither approach is perfect. I still prefer the variable over the constant. I have never done any benchmark tests to see if there is any significant performance difference. Have you? if you have a lot of debugging code, it can make

Re: Debugging and passing constant value at run time

g Cc: "Ron Bergin" Sent: Tuesday, July 7, 2015 7:41:34 AM Subject: Re: Debugging and passing constant value at run time On Tue, 7 Jul 2015 07:27:49 -0700 (PDT) Ron Bergin wrote: > Using a DEBUG constant and assigning its value via an environment > variable are both common, but has a

Re: Debugging and passing constant value at run time

On Tue, 7 Jul 2015 07:27:49 -0700 (PDT) Ron Bergin wrote: > Using a DEBUG constant and assigning its value via an environment > variable are both common, but has a drawback and would not be my > choice of approach. I prefer to use a lexical var (with file scope) > and assign it via command line o

Re: Debugging and passing constant value at run time

> \$VERBOSE ); if( $DEBUG ){ say 'hello'; say 'goodbye' if $VERBOSE > 1; } Ron From: "Sharanbasappa Raghapur, ERS, HCLTech" To: "Perl Beginners" Sent: Tuesday, July 7, 2015 4:40:35 AM Subject: Debugging and passing constant value at run t

Re: Debugging and passing constant value at run time

On Tue, 7 Jul 2015 11:40:35 + "Sharanbasappa Raghapur, ERS, HCLTech" wrote: > I am using constant mainly to enable printing of debugging messages > (e.g. use constant DEBUGGING_L1 => 0;) Normally, the value is '0' and > when I need to see debug messages,

Debugging and passing constant value at run time

Hi, I am using constant mainly to enable printing of debugging messages (e.g. use constant DEBUGGING_L1 => 0;) Normally, the value is '0' and when I need to see debug messages, I make this 1 and run the script. Is there a way to allocate value to constants at run time so tha

Re: Debugging a PERL Web Application

de, asking for help here is by far the most effective debugging aid you'll ever get, incidentally : ). Personally though, I'd think the best debugger is nothing but a bunch of trusty old prints[2]. Also, please, It's Perl or perl, but never PERL[3]. Brian. [0] http://pa

Debugging a PERL Web Application

Hi, I have started working with Perl since 3 days. I would like to debug an existing perl-web application and have already found a few links on how to use eclipse and EPIC. Here I am stuck though and I hope someone here has already found the answer to my question. In this link: http://www.epic-id

Re: How to complete the loop while debugging.

Thanks to this Robert as well :) it worked Cheers, Parag On Tue, Nov 17, 2009 at 11:05 PM, Robert Wohlfarth wrote: > On Tue, Nov 17, 2009 at 11:11 AM, Parag Kalra wrote: > >> It happens so many times that while debugging I come inside a loop which >> doesn't

Re: How to complete the loop while debugging.

t; Coventry HealthCare > 3220 Keller Springs > Suite #106 > Carrollton, Texas 75006 > (o) (972) 725-1484 > (e) gorrebeec...@cvty.com > > -Original Message- > From: Parag Kalra [mailto:paragka...@gmail.com] > Sent: Tuesday, November 17, 2009 11:11 AM > To: Perl Beginners

Re: How to complete the loop while debugging.

On Tue, Nov 17, 2009 at 11:11 AM, Parag Kalra wrote: > It happens so many times that while debugging I come inside a loop which > doesn't contain the issue which I am debugging. > > And as I am not aware of a method to complete the loop while debugging - I > manually enter

How to complete the loop while debugging.

Hi All, It happens so many times that while debugging I come inside a loop which doesn't contain the issue which I am debugging. And as I am not aware of a method to complete the loop while debugging - I manually enter 'n' to complete each iteration and finish the loop operation.

Re: Debugging and tests

> On Wed, Jul 8, 2009 at 10:16, Steve Bertrand wrote: >> %hash = map { my $x = $_; $_ =~ s/h_/hello_/;$_, $hash{$x} } keys %hash; > snip > > The following bits of advice are stylistic in nature, so you can > ignore them, but there really are good reasons not to. > > As name, $x does not really mea

Re: Debugging and tests

On Wed, Jul 8, 2009 at 10:16, Steve Bertrand wrote: snip > I agree, and just before you mailed, I did figure out that I needed a > placeholder, by using your recommended 'w' command in the debugger. It's > a tiny bit different than your approach, but it works ;) > > %hash = map { my $x = $_; $_ =~

Re: Debugging and tests

Chas. Owens wrote: > On Wed, Jul 8, 2009 at 09:31, Steve Bertrand wrote: > snip >> my %newhash = map { $_ =~ s/h_/hello_/; ($_, $hash{$_}) } keys %hash; > snip > > That will still have a problem: $_ is changed, so it won't reference > the correct thing in %hash. Try this instead: > > my %newhash

Re: Debugging and tests

On Wed, Jul 8, 2009 at 09:31, Steve Bertrand wrote: snip > my %newhash = map { $_ =~ s/h_/hello_/; ($_, $hash{$_}) } keys %hash; snip That will still have a problem: $_ is changed, so it won't reference the correct thing in %hash. Try this instead: my %newhash = map { (my $k = $_) =~ s/h_/hello_

Re: File::Find with chmod trouble debugging

Telemachus writes: > On Mon Jul 06 2009 @ 3:31, Harry Putnam wrote: >> Thanks to all ... >> Now I'm curious about something else: >> >> Is the mode in a stat(file) readout something still different >> than octal or decimal? > > As John answered, there's more there than just the permissions. If

Re: Debugging and tests

Steve Bertrand wrote: > Hi everyone, > > I've got a couple of simple questions. First, I know that the below line > is not correct, but instead of having someone correct it, I'd rather > learn more about the Perl debugger, and the map function. > > I'd like to replace 'h_' with 'hello_' in each k

Debugging and tests

Hi everyone, I've got a couple of simple questions. First, I know that the below line is not correct, but instead of having someone correct it, I'd rather learn more about the Perl debugger, and the map function. I'd like to replace 'h_' with 'hello_' in each key name in %hash, but warnings indic

Re: File::Find with chmod trouble debugging

On Mon Jul 06 2009 @ 3:31, Harry Putnam wrote: > Thanks to all ... > Now I'm curious about something else: > > Is the mode in a stat(file) readout something still different > than octal or decimal? As John answered, there's more there than just the permissions. If you check perldoc -f stat, ther

Re: File::Find with chmod trouble debugging

Harry Putnam wrote: Thanks to all ... Now I'm curious about something else: Is the mode in a stat(file) readout something still different than octal or decimal? I see `33261' show up in the `mode' slot on a file with 755 permissions (from perldoc -f stat: [...] ($dev,$ino,$mode,$nli

Re: File::Find with chmod trouble debugging

Thanks to all ... Now I'm curious about something else: Is the mode in a stat(file) readout something still different than octal or decimal? I see `33261' show up in the `mode' slot on a file with 755 permissions (from perldoc -f stat: [...] ($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$si

Re: File::Find with chmod trouble debugging

On Mon Jul 06 2009 @ 7:00, Harry Putnam wrote: > Can anyone tell me how printing of $mode = 0755 turns into 493? Yup: what's in $mode is an octal number. Its decimal equivalent is 493. What you really want to print out is the string '0755', but the string and the octal number are not the same thi

Re: File::Find with chmod trouble debugging

On Mon, Jul 6, 2009 at 08:00, Harry Putnam wrote: snip > Can anyone tell me how printing of $mode = 0755 turns into 493? snip >  my $mode = 0755; snip >             print "hpdb chmod $mode  $fname\n"; snip 0755 is 493. More specifically they are two representations of the same number: the first i

AW: File::Find with chmod trouble debugging

Harry Putnam asked: > The script below is my first usage of perls `chmod', but it appears to > be in keeping with the info at perldoc -f chmod. > > But somehow in the print of $mode it turns into 493... even though it > is set to 755. Its just the print though... the actual chmod appears > to be

File::Find with chmod trouble debugging

The script below is my first usage of perls `chmod', but it appears to be in keeping with the info at perldoc -f chmod. But somehow in the print of $mode it turns into 493... even though it is set to 755. Its just the print though... the actual chmod appears to be working as expected. Can anyon

Re: MIME::Lite debugging

2008/10/26 AaronLS <[EMAIL PROTECTED]>: > I am trying to modify an existing script that uses MIME::Lite->send > > I am trying to take any debug output and send it through a Debug > function which goes to a log file so I can see if there is an error. > Am I doing this correctly?: > > I'm not using d

MIME::Lite debugging

I am trying to modify an existing script that uses MIME::Lite->send I am trying to take any debug output and send it through a Debug function which goes to a log file so I can see if there is an error. Am I doing this correctly?: I'm not using die because I think that sends it to stdout. The do

Re: debugging code that freezes

On Thu, 06 Mar 2008 00:13:02 -0700, Joseph L. Casale wrote: > In another list, I am baffled by the instability of a Perl script that > freezes after some time for a user. What can be done to run a Perl > script in a debug like mode such that all system calls could be logged so that > one could see

RE: debugging code that freezes

Joseph L. Casale <[EMAIL PROTECTED]> asked: > In another list, I am baffled by the instability of a Perl > script that freezes after some time for a user. What can be > done to run a Perl script in a debug like mode such that all > system calls could be logged so that one could see what was > a

debugging code that freezes

In another list, I am baffled by the instability of a Perl script that freezes after some time for a user. What can be done to run a Perl script in a debug like mode such that all system calls could be logged so that one could see what was attempted for execution by the script as it hung? Thank

Re: Strange debugging question...

"Zachary Shay" schreef: > Is there any way to get the name of a variable by knowing its memory > address? Do you consider its ref-value as its memory address? -- Affijn, Ruud "Gewoon is een tijger." -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

Re: Strange debugging question...

On Sep 27, 6:11 pm, [EMAIL PROTECTED] (Zachary Shay) wrote: > Is there any way to get the name of a variable by knowing its memory > address? Not in general in a reasonable time. Anyhow, how would you know the address of a variable in Perl? What do you mean by "the name"? An SV in Perl can have

Re: Strange debugging question...

On Thu, Sep 27, 2007 at 01:11:11PM -0400, Zachary Shay wrote: > Is there any way to get the name of a variable by knowing its memory > address? Some hairy XS might get you an 80% solution, but in general, no. -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net -- To unsubscribe, e-mail: [

Strange debugging question...

Is there any way to get the name of a variable by knowing its memory address? Thanks, Zach

Re: debugging Perl/XS

Chas Owens wrote: On 8/31/07, Robert Hicks <[EMAIL PROTECTED]> wrote: Are there any pointers somewhere? snip The following url seems like it might be helpful; unfortunately I can't seem to break my bad habit of debugging with print/printf, so I haven't tried to use a real

Re: debugging Perl/XS

On 8/31/07, Robert Hicks <[EMAIL PROTECTED]> wrote: > Are there any pointers somewhere? snip The following url seems like it might be helpful; unfortunately I can't seem to break my bad habit of debugging with print/printf, so I haven't tried to use a real debugger

debugging Perl/XS

Are there any pointers somewhere? Robert -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/

Re: debugging

On Jun 5, 6:27 am, [EMAIL PROTECTED] (Zentara) wrote: > On Mon, 04 Jun 2007 05:27:25 -0700, [EMAIL PROTECTED] (SPX2) > wrote: > > >hi, > >im getting serious with perl and i need debugging, > >ofcourse im not reffering to command line debugging. > >i find ddd to

debugging

hi, im getting serious with perl and i need debugging, ofcourse im not reffering to command line debugging. i find ddd to be good on linux but on windows i cant find anything that will work fast enough. komodo is very slow on my comp. visual studio .net works ...decent would visual perl be an

Re: debugging Perl with the Eclipse IDE

http://www-128.ibm.com/developerworks/edu/os-dw-os-epic-i.html?S_TACT=105AGX44&S_CMP=ECL That is a debugging tutorial off the EPIC site. Maybe it has an answer in there somewhere. Robert -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] &

Re: debugging Perl with the Eclipse IDE

On 7/29/06, Daniel D Jones <[EMAIL PROTECTED]> wrote: Unable to connect to remote host: 192.168.1.12:5000 Compilation failed in require. at /home/ddjones/workspace/Temp/puzzle.pl line 0 main::BEGIN() called at /usr/lib/perl5/5.8.8/perl5db.pl line 0 eval {...} called at /usr/lib/

debugging Perl with the Eclipse IDE

I'm not sure if this is a Perl problem or an Eclipse problem, but I'm hoping someone here will know the solution. I'm trying to debug Perl under the Eclipse IDE. I recently reconfigured my network, which resulted in changing my local IP from 192.168.1.12 to 192.168.2.12. When I try to run the

Re: debugging question

iable set to 'vt100'. It will start up another xterm debugging the child process on forking. -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://

Re: debugging question

On Thu, 20 Apr 2006 11:15:02 +0200, Gergely Buday wrote: > Is there a way to debug concurrent perl programs, i.e. programs that > use fork()? E.g. I would like to watch the main process. At a naive > try I got strange error messages. Correction to my previous post; TERM should be set to 'xterm'.

debugging question

Is there a way to debug concurrent perl programs, i.e. programs that use fork()? E.g. I would like to watch the main process. At a naive try I got strange error messages. - Gergely -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: print interactive debugging info into a file

On Sat, 18 Feb 2006 16:20:10 +0800, Ken Perl wrote: > The "DB::OUT" filehandle is opened to /dev/tty, regardless of where > STDOUT may be redirected to, so it's impossible to print the > interactive debugging info into a file? > I tried 'x @session >/tmp/da

print interactive debugging info into a file

The "DB::OUT" filehandle is opened to /dev/tty, regardless of where STDOUT may be redirected to, so it's impossible to print the interactive debugging info into a file? I tried 'x @session >/tmp/data' in the debugger and didn't work. -- perl -e &#x

Re: test/debugging modules that are duplicates of existing modules.

Tom Allison am Donnerstag, 13. Oktober 2005 12.52: > I'm pretty sure I'm not doing this right. > > I have two modules of the same name, current version and future version, > in two different directories. > > $HOME/test/Module1.pm > $HOME/test/Module2.pm > $HOME/lib/Module1.pm > $HOME/lib/Module2.pm

Re: test/debugging modules that are duplicates of existing modules.

On Thu, 13 Oct 2005 06:52:52 -0400, Tom Allison wrote: > I have two modules of the same name, current version and future version, > in two different directories. > > $HOME/test/Module1.pm > $HOME/test/Module2.pm > $HOME/lib/Module1.pm > $HOME/lib/Module2.pm > > and another module: $HOME/lib/Mod

test/debugging modules that are duplicates of existing modules.

I'm pretty sure I'm not doing this right. I have two modules of the same name, current version and future version, in two different directories. $HOME/test/Module1.pm $HOME/test/Module2.pm $HOME/lib/Module1.pm $HOME/lib/Module2.pm and another module: $HOME/lib/Module3.pm Under perl -d I can

Debugging AUTOLOAD functions

Hello everyone, I am trying to debug perl code. A function call is autoloaded and when i step into it, it takes me to perl AUTOLOAD call, returning from there gets me back to main file executing the funtion. Is there any special settings/procedure i should follow? thanks in advance, lohit

debugging XS code.

Hi, I am running perl-5.8.6 on z/OS. How do I debug XS code ? 1) I have a specific function "static SV *encode_method()" in a xs file. The fn name remains the same in the corresponding c file. I am unable to break at this fn within the c file although perl is built with -g. Any thoughts on how t

Re: Debugging OpenPerlIDE

From: "Siegfried Heintze" <[EMAIL PROTECTED]> > I love the Perl IDE/debugger I found on source forge. Unfortunately, > it only works for me on NT4/Perl 5.6. When I try to run it on Win2003 > server, the following line fails (in the file perl5db.pl that comes > with the debugger): > > my $resul

Debugging OpenPerlIDE

I love the Perl IDE/debugger I found on source forge. Unfortunately, it only works for me on NT4/Perl 5.6. When I try to run it on Win2003 server, the following line fails (in the file perl5db.pl that comes with the debugger): my $result = Win32::GetFullPathName($filename); It seems to

disabling Perl "threads" and "debugging" to allow DBI install

I have tried to install the DBI module for Perl and experienced the bug mentioned in the DBI Readme file: Note: There is a bug in perl 5.8.2 when configured with threads and debugging enabled (bug #24463) which causes a DBI test to fail. How can I disable "threads" and "debuggi

RE: Debugging(perl -d)

> -Original Message- > From: Mike Ni [mailto:[EMAIL PROTECTED] > Sent: Monday, 15 March 2004 10:43 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Debugging(perl -d) > > Hey, > > I was handed several perl files written for the Apache >

Debugging(perl -d)

Hey, I was handed several perl files written for the Apache Web Server. The person who wrote these isn't here any more. I need to trace and document the perl files. I udnerstand there is a built-in debuuger come with the perl - "!perl -d". However, since these perl files were wriitten for the

RE: Enable Perl Debugging at Run-Time

> -Original Message- > From: WC Jones [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 10 March 2004 11:55 AM > To: David le Blanc > Subject: Re: Enable Perl Debugging at Run-Time > > On Wed, Mar 10, 2004 at 11:15:39AM +1100, David le Blanc wrote: > > &g

RE: Enable Perl Debugging at Run-Time

> -Original Message- > From: zentara [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 10 March 2004 1:41 AM > To: [EMAIL PROTECTED] > Subject: Re: Enable Perl Debugging at Run-Time > > On Tue, 9 Mar 2004 12:07:18 +1100, > [EMAIL PROTECTED] (David Le Blanc) w

Enable Perl Debugging at Run-Time

cal DB::DB function which performs the tracing to module mytrace; sub DB::DB() { ... trace code which traces to $_TRACE_FH if $_TRACE } sub trace_to { open( $_TRACE_FH, "$logfile"); $_TRACE = 1; } (2) Start debugging via the command line #!perl -d -w (3) Configure APA

Re: Debugging Problem: Phantom line numbers!

"Christopher D . Lewis" wrote: > > ... and I have no idea what an explicit package name is :-) At your > request, I have placed the whole, ugly thing at > www.PuckU.org/misc/nudice-01c for inspection of why Perl thinks the > line numbers are as it reports ... I apologize in advance for the > prog

Re: Debugging Problem: Phantom line numbers!

"Christopher D . Lewis" wrote: > > On Tuesday, January 7, 2003, at 11:19 AM, Peter Scott wrote: > > > [responding to replacement of sub displayResults with {print __LINE__ > > . " sub displayResults";}] > > That needs to be __LINE__, not __line__. The above is an error. > > You do have -w and u

Re: Debugging Problem: Phantom line numbers!

On Tuesday, January 7, 2003, at 11:19 AM, Peter Scott wrote: [responding to replacement of sub displayResults with {print __LINE__ . " sub displayResults";}] That needs to be __LINE__, not __line__. The above is an error. You do have -w and use strict in this program, right? When I use "__LI

Re: Debugging Problem: Phantom line numbers!

At 06:16 PM 1/7/03 -0600, Christopher D. Lewis wrote: >On Tuesday, January 7, 2003, at 11:19 AM, Peter Scott wrote: > >>[responding to replacement of sub displayResults with {print __LINE__ >>. " sub displayResults";}] >>That needs to be __LINE__, not __line__. The above is an error. >>You do ha

Re: Debugging Problem: Phantom line numbers!

Good tip, Peter, Joseph Peter Scott wrote: > In article <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] (Christopher D . Lewis) writes: > > > >On Tuesday, January 7, 2003, at 10:31 AM, Peter Scott wrote: > > > >> [EMAIL PROTECTED] (Christopher D . Lewis) writes: > >>> My problem is that the errors P

Re: Debugging Problem: Phantom line numbers!

Hi Chris Simplifying sub displayResults is a Good Thing. It should actually be: sub displayResults { print __LINE__ . "sub displayResults\n"; } but it should compile as it is, yet the parser's still complaining about it. I would guess that there's something wrong with the lines immediately p

Re: Debugging Problem: Phantom line numbers!

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Christopher D . Lewis) writes: > >On Tuesday, January 7, 2003, at 10:31 AM, Peter Scott wrote: > >> [EMAIL PROTECTED] (Christopher D . Lewis) writes: >>> My problem is that the errors Perl coughs up end with: >>> >>> syntax error at ./nudice-01c

Re: Debugging Problem: Phantom line numbers!

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Christopher D . Lewis) writes: > >On Tuesday, January 7, 2003, at 10:31 AM, Peter Scott wrote: > >> >> What line numbers do your text editors say the above statements are >> actually on? >>> the errors Perl coughs up end with: >>> >>> syntax erro

Re: Debugging Problem: Phantom line numbers!

On Tuesday, January 7, 2003, at 10:31 AM, Peter Scott wrote: [EMAIL PROTECTED] (Christopher D . Lewis) writes: My problem is that the errors Perl coughs up end with: syntax error at ./nudice-01c line 187, near "sub displayResults " syntax error at ./nudice-01c line 305, near "sub rollRequest

Re: Debugging Problem: Phantom line numbers!

On Tuesday, January 7, 2003, at 10:31 AM, Peter Scott wrote: What line numbers do your text editors say the above statements are actually on? the errors Perl coughs up end with: syntax error at ./nudice-01c line 187, near "sub displayResults " the text "sub displayResults " occurs on line

Re: Debugging Problem: Phantom line numbers!

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Christopher D . Lewis) writes: >Dear all, > I'm writing (as a practice piece, all the better to learn Perl coding) >what is for me a big, complicated program which has lots of options and >output possibilities. And ... heh, heh ... it isn

Debugging Problem: Phantom line numbers!

Dear all, I'm writing (as a practice piece, all the better to learn Perl coding) what is for me a big, complicated program which has lots of options and output possibilities. And ... heh, heh ... it isn't working. My problem is that the errors Perl coughs up end with: syntax error at ./nudic

Re: Debugging

In article <007f01c26596$989cd530$0300a8c0@jessee>, [EMAIL PROTECTED] (Jessee Parker) writes: >Is there any way to use the perl debugger to step through a script that >forks a child (step into the child I guess is what I am asking)? Yes. Run the program in an xterm window and the debugger will

Debugging

Is there any way to use the perl debugger to step through a script that forks a child (step into the child I guess is what I am asking)? I have a script that forks a copy of itself to act as a daemon. I've noticed that when the script runs, the load average on the system steadily rises. Jessee

Re: Perl debugging: dumpvar.pl Data::Dumper Dumpvalue et al?

In article <001501c254d3$2666a910$3864a8c0@comice>, [EMAIL PROTECTED] (Jeff Aa) writes: >I have used Perl for a while, and always used dumpvar.pl / Plze don't. AFAIK the only thing in the core that uses it is the debugger. I would so love to deprecate it. You think it's hard to use, you s

Perl debugging: dumpvar.pl Data::Dumper Dumpvalue et al?

I have used Perl for a while, and always used dumpvar.pl / main::dumpvalue() to dump out things (I guess that tells you how long! 8-)) I had a look at Data::Dumper - but its dumps are either too terse (i.e. all one line) or too verbose (i.e. I am dumping data structures and don't really need to w

Re: Best Practices for Debugging and Error Handling in CGIScripts?

use CGI::Carp qw(fatalsToBrowser) tail -f The 2 best tools out there! =) John Pitchko Data Services Saskatchewan Government Insurance >>> "David Simcik" <[EMAIL PROTECTED]> 08/15/02 12:21pm >>> Can anyone list some resources or methods they use for debug

Best Practices for Debugging and Error Handling in CGI Scripts?

Can anyone list some resources or methods they use for debugging (Perl) CGI scripts. How can I use CGI::Carp most effectively? Does anyone have any recommended practices for graceful CGI error handling? Is this something that should be built in a custom module for my site? Sorry if these are

Re: Debugging the debugger

Paul Johnson <[EMAIL PROTECTED]> writes: > The text is still there in the latest release candidate for Perl 5.8.0. > If anyone feels like saving the world, now would be a very good time to > do it. In other words, documentation patches are still being accepted. That would first require one to u

Re: Debugging the debugger

On Mon, Jun 24, 2002 at 10:10:38PM -0700, Harry Putnam wrote: > The documentation in TERM::Readline at ENVIRONMENT reads like maybe > some kind of cut and paste editing went wrong or something. It reads > like gibberish. The usage of the words `head' `tail' and `ornaments' > is confusing to the

Re: Debugging the debugger

Bob Showalter <[EMAIL PROTECTED]> writes: >> Anyone have an idea what might be causing this? >> Can it be readline? > > I have this problem using Putty and FreeBSD. I was able to fix it by > adding the following to my .bashrc: > >export "PERL_RL= o=0" > > This was documented in perldoc Term::

RE: Debugging the debugger

> -Original Message- > From: Harry Putnam [mailto:[EMAIL PROTECTED]] > Sent: Sunday, June 23, 2002 3:13 AM > To: [EMAIL PROTECTED] > Subject: Debugging the debugger > > > Just going thru the debug tutorial: >perldoc perldebtut > Following along havin

Re: Debugging the debugger

At 09:33 AM 6/23/02 -0700, Harry Putnam wrote: >Peter Scott <[EMAIL PROTECTED]> writes: > > > print "Hello\n" > > > > at a debugger prompt. > >Yeah, it gives the same chopping action: >main::(./temp:2): e strict; > DB<1> print "Hello\n" H >ello >

Re: Debugging the debugger

Peter Scott <[EMAIL PROTECTED]> writes: > print "Hello\n" > > at a debugger prompt. Yeah, it gives the same chopping action: main::(./temp:2): e strict; DB<1> print "Hello\n" H ello DB<2> Any ideas how to correct this? -- To unsubscribe, e

Re: Debugging the debugger

At 12:13 AM 6/23/02 -0700, Harry Putnam wrote: >Just going thru the debug tutorial: >perldoc perldebtut >Following along having writen the example script to disk. >I notice any `p' commands gives me a line with the first character >chopped off. > >Like when the tutorial gets to the part where

Debugging the debugger

Just going thru the debug tutorial: perldoc perldebtut Following along having writen the example script to disk. I notice any `p' commands gives me a line with the first character chopped off. Like when the tutorial gets to the part where you `p $key', I get elcome instead of Welcome. Actual

Re: debugging statements and such

From: David T-G <[EMAIL PROTECTED]> > The recent post containing print statements "this is one" and so on > reminded me of an old question that I've never had answered: what's a > good way to trace your program as it runs, preferably without getting > into the debugger? You migh

Re: debugging statements and such

ich in any Perl program worth its salt are generally too numerous to want to do this. However, you can show a subset if you want. I show one example on page 119 of my book "Perl Debugged", which, amazingly enough, is about debugging Perl programs: while () { $DB::trace = 1, next if

Re: debugging statements and such

on Fri, 07 Jun 2002 12:31:52 GMT, [EMAIL PROTECTED] (David T-G) wrote: > The recent post containing print statements "this is one" and so > on reminded me of an old question that I've never had answered: > what's a good way to trace your program as it runs, preferably > without getting into the

  1   2   >