Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 81502 - working script fails under debugger with perl-5.8.0-82
working script fails under debugger with perl-5.8.0-82
Product: Red Hat Raw Hide
Classification: Retired
Component: perl (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-01-09 17:55 EST by Jonathan Kamens
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-28 03:28:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Kamens 2003-01-09 17:55:43 EST
I have a script which fails as follows when run under the debugger (i.e., just
start the script with "perl -d <script> <args>" and type "c RET") but not when
run without the debugger:

print() on unopened filehandle old_watch at
/home/jik/dev/bulkmail/bounces/filter.pl line 136, <> chunk 1.
        DB::DB called at /home/jik/dev/bulkmail/bounces/filter.pl line 111
Can't coerce GLOB to string in concat at
/home/jik/dev/bulkmail/bounces/filter.pl line 136, <> chunk 1.
        DB::DB called at /home/jik/dev/bulkmail/bounces/filter.pl line 111
Debugged program terminated.  Use q to quit or R to restart,

The code around line 136 looks like this:

   133		    $count++;
   135		    if (! &filter($_)) {
   136		      print_it:
   137			print(FILTEROUT $orig) || die "write to $filter_output: $!";
   138		    }
   139		}
   140	    }

Note that the failure happens right after a call to "goto print_it" from
elsewhere in the script.

Unfortunately, I can't find a simple test case for the problem, and I can't send
you the whole script because it's proprietary.
Comment 1 Warren Togami 2005-05-28 03:28:02 EDT
We cannot possibly solve problems that we cannot reproduce due to lack of source
code or simple test case.  Sorry.

Note You need to log in before you can comment on or make changes to this bug.