Sponsored Content
Top Forums Shell Programming and Scripting Methods For Debugging Perl Problems Post 302544309 by DGPickett on Wednesday 3rd of August 2011 12:08:20 PM
Old 08-03-2011
If you write code that trusts no input, checks and logs errors, leaves nothing to chance but does something for every logical possibility, then your challenges will be small enough for debug statements or side code tests. You, too, deserve a nice error log, one per run or with headings and exit trailers. That is why there is always an fd 2 stderr 2>log_file in UNIX.

I mostly use gdb for core dumps in c/c++ dev, to get a stack trace.

For apps with lots of system calls, strace/truss/tusc is great, can even be used when code is already running, when you have no source! Sometimes you can option it to tell you every library call in C, which you can relate to PERL actions.

Good luck.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Problems with perl

hi i'm writing multiclient perl server cross plataform it will redirect one connection to any computer inside mine lan so when someone connect on this server it create a socket and connect to the computer create two threads and read the data incoming from the client and send to another... (0 Replies)
Discussion started by: sendai
0 Replies

2. Shell Programming and Scripting

problems with double quotes in PERL

I have a cgi script I run through apache2 and I need to have a line that contains double quotes within double quotes. Here's what I need PERL to pass to rrdtool: HRULE:30#BBBB00:"30.0 constant":dashesIt's a little more complicated since I also have variables in the statement which requires... (13 Replies)
Discussion started by: audiophile
13 Replies

3. Shell Programming and Scripting

Perl - Problems with Signal Handler

I have a problem with signal handlers not working. I have a long 1000 line code and somehow this code for signal handling is not working: $SIG{INT} = \&interrupt; sub interrupt { print STDERR "Caught a control c!\n"; exit; # or just about anything else you'd want to do } Any... (2 Replies)
Discussion started by: som.nitk
2 Replies

4. UNIX for Dummies Questions & Answers

Problems with Alt Gr in Perl scripts

Hey I am new to programming in general but am trying to work in Perl. The thing is that almost every time I write a script (I use nedit) I get problems with Alt Gr. E.g. In stead of } I get <gs> or in stead of \ nothing happens. Sometimes it's really bad and when I want a new line then... (1 Reply)
Discussion started by: Banni
1 Replies

5. Shell Programming and Scripting

Methods to SSH (Perl)...

Can anyone break down the different methods of using SSH in perl? I'm currently using Net::SSH::Expect, which allows me to login to a machine and execute multiple commands without having to ssh again. This feature of holding the session works well for me, but it's slow. If I set timeouts to 4... (3 Replies)
Discussion started by: mrwatkin
3 Replies

6. Shell Programming and Scripting

Turning on Debugging for a perl script

for security reasons I can not post any part of the script in question in this thread. i hope im not breaking any rules by not doing so. but i have a perl script that i've been asked to turn on debugging on. i didn't write this perl script and i have very very little knowledge of perl. so i... (3 Replies)
Discussion started by: SkySmart
3 Replies

7. Shell Programming and Scripting

Perl Methods Calling

Hello I am on my way to improve my wonderful Perl skills, I got an issue which I want to share with you all. I have a Perl module which looks like package Cocoa; require Exporter; @ISA = qw(Exporter); my $a=''; my $b=''; my $c=''; sub new { my $this = shift; # Create... (8 Replies)
Discussion started by: adisky123
8 Replies

8. Red Hat

Perl problems in RHEL 5.X

Hi, We have RHEL 5.X OS installed here, where we need few Perl modules installed. I have local copy of Perl modules in .tar.gz format. The problem is that we don't have Internet available here and it is really pain to install all the modules manually on all the servers one by one. So can I... (1 Reply)
Discussion started by: nixhead
1 Replies

9. Shell Programming and Scripting

Debugging mysterious perl script problem

the attached perl script is a deamon that, once kicked off from the command line, it runs in the background and waits for the master server to tell it what plugins to run. the script works well. but the problem is, whenever i start it, after about a few seconds of starting it, i start getting... (4 Replies)
Discussion started by: SkySmart
4 Replies
PROVE(1)						 Perl Programmers Reference Guide						  PROVE(1)

NAME
prove -- A command-line tool for running tests against Test::Harness SYNOPSIS
prove [options] [files/directories] OPTIONS
-b, --blib Adds blib/lib to the path for your tests, a la "use blib" -d, --debug Includes extra debugging information -D, --dry Dry run: Show the tests to run, but don't run them -h, --help Display this help -H, --man Longer manpage for prove -I Add libraries to @INC, as Perl's -I -l, --lib Add lib to the path for your tests --perl Sets the name of the Perl executable to use -r, --recurse Recursively descend into directories -s, --shuffle Run the tests in a random order --strap Define strap class to use -T Enable tainting checks -t Enable tainting warnings --timer Print elapsed time after each test file -v, --verbose Display standard output of test scripts while running them -V, --version Display version info Single-character options may be stacked. Default options may be set by specifying the PROVE_SWITCHES environment variable. OVERVIEW
prove is a command-line interface to the test-running functionality of "Test::Harness". With no arguments, it will run all tests in the current directory. Shell metacharacters may be used with command lines options and will be exanded via "File::Glob::bsd_glob". PROVE VS. ";MAKE TEST" prove has a number of advantages over "make test" when doing development. * prove is designed as a development tool Perl users typically run the test harness through a makefile via "make test". That's fine for module distributions, but it's subopti- mal for a test/code/debug development cycle. * prove is granular prove lets your run against only the files you want to check. Running "prove t/live/ t/master.t" checks every *.t in t/live, plus t/master.t. * prove has an easy verbose mode prove has a "-v" option to see the raw output from the tests. To do this with "make test", you must set "HARNESS_VERBOSE=1" in the environment. * prove can run under taint mode prove's "-T" runs your tests under "perl -T", and "-t" runs them under "perl -t". * prove can shuffle tests You can use prove's "--shuffle" option to try to excite problems that don't show up when tests are run in the same order every time. * prove doesn't rely on a make tool Not everyone wants to write a makefile, or use ExtUtils::MakeMaker to do so. prove has no external dependencies. * Not everything is a module More and more users are using Perl's testing tools outside the context of a module distribution, and may not even use a makefile at all. COMMAND LINE OPTIONS
-b, --blib Adds blib/lib to the path for your tests, a la "use blib". -d, --debug Include debug information about how prove is being run. This option doesn't show the output from the test scripts. That's handled by -v,--verbose. -D, --dry Dry run: Show the tests to run, but don't run them. -I Add libraries to @INC, as Perl's -I. -l, --lib Add "lib" to @INC. Equivalent to "-Ilib". --perl Sets the "HARNESS_PERL" environment variable, which controls what Perl executable will run the tests. -r, --recurse Descends into subdirectories of any directories specified, looking for tests. -s, --shuffle Sometimes tests are accidentally dependent on tests that have been run before. This switch will shuffle the tests to be run prior to run- ning them, thus ensuring that hidden dependencies in the test order are likely to be revealed. The author hopes the run the algorithm on the preceding sentence to see if he can produce something slightly less awkward. --strap Sets the HARNESS_STRAP_CLASS variable to set which Test::Harness::Straps variable to use in running the tests. -t Runs test programs under perl's -t taint warning mode. -T Runs test programs under perl's -T taint mode. --timer Print elapsed time after each test file -v, --verbose Display standard output of test scripts while running them. Also sets TEST_VERBOSE in case your tests rely on them. -V, --version Display version info. BUGS
Please use the CPAN bug ticketing system at <http://rt.cpan.org/>. You can also mail bugs, fixes and enhancements to "<bug-test-har- ness@rt.cpan.org>". TODO
o Shuffled tests must be recreatable AUTHORS
Andy Lester "<andy at petdance.com>" COPYRIGHT
Copyright 2004-2006 by Andy Lester "<andy at petdance.com>". This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See <http://www.perl.com/perl/misc/Artistic.html>. perl v5.8.9 2009-04-13 PROVE(1)
All times are GMT -4. The time now is 08:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy