hlampert has asked for the wisdom of the Perl Monks concerning the following question:

On Windows XP, debugging any program, when the debugger starts the first time everything is fine. Press 'R' to restart the debugger and the following messages appear: 
Warning: some settings and command-line options may be lost!
Your vendor has not defined POSIX macro _SC_OPEN_MAX used at c:/Perl/l
+ib/perl5db.pl line 3296
  at c:/Perl/lib/POSIX.pm line 47
      POSIX::AUTOLOAD() called at c:/Perl/lib/perl5db.pl line 3296
      DB::DB called at u:/perlScripts/temp.pl line 3

[download]
Pressing the 'R' key again at the debugger prompt after these messages appear yields: 
Warning: some settings and command-line options may be lost!
Your vendor has not defined POSIX macro _SC_OPEN_MAX used at c:/Perl/l
+ib/perl5db.pl line 3296
END failed--call queue aborted at u:/perlScripts/temp.pl line 269
  at u:/perlScripts/temp.pl line 269

Debugger exited abnormally with code 9
---------------------

[download]
The temp.pl program is a simple hello world script which doesn't have anywhere near 269 lines of code. This is a new phenomenon, I don't recall this happening before upgrading from 5.8.4. Any help would be appreciated.

Replies are listed 'Best First'.
Re: Perl Debugger v1.28 can't be restarted in Activestate Perl Ver 5.8.7 build 815?
by Corion (Patriarch) on Dec 12, 2005 at 15:19 UTC

    I guess the problem comes from the Perl debugger restarting itself via exec $0 ..., which is only emulated under Windows and thus quite unlikely to work at all. If you look in C:/Perl/lib/perl5db.pl, line 3296 (in my case, it was line 2800), there is the handling of the R letter/command. The line number and error refer to an error in perl5db.pl and not an error in your script.

    The change in behaviour likely stems from changes in the C-code of POSIX.pm or Perl itself.

[reply]
[d/l]
[select]
      Thanks for your thoughts - I know it used to work and now it doesn't. I'm sorry I'm not enough of a genuius to dig through the internals of POSIX.pm or the debugger - but I wish there WAS a genius out there who cared enough to make it work again...
[reply]
Re: Perl Debugger v1.28 can't be restarted in Activestate Perl Ver 5.8.7 build 815?
by QM (Parson) on Dec 12, 2005 at 15:11 UTC
    Just for perspective (and not solving your problem)...I've never been able to restart the debugger on Windoze. I've always had the same message. This was under several Perl versions from Activestate. Long ago I had the non-Activestate build, but I don't recall if it had the same problem, as I was new to Perl, and didn't use the debugger.

    Perhaps someone else will be able to give a reason for this behavior, or even better, a fix.

    -QM
    --
    Quantum Mechanics: The dreams stuff is made of

[reply]
Re: Perl Debugger v1.28 can't be restarted in Activestate Perl Ver 5.8.7 build 815?
by swampyankee (Parson) on Dec 12, 2005 at 15:23 UTC

    I've had similar experience on all 5.8 versions of ActiveState's Perl. I find it mildly aggravating, especially as I can remember the debugger being re-startable before 5.8.

    My only advice is to submit a bug report to ActiveState.

    emc

    Visit Netlib
[reply]
      Well, I _know_ that 503 worked, so this is something new. Anyway, I commented out the POSIX call in perl5db.pl (It defaults to a reasonable value anyway) and things are all good again with ActiveState 5.8.8. Give it a try, may work for you. (The call started on line 3331.) Robert
[reply]
Re: Perl Debugger v1.28 can't be restarted in Activestate Perl Ver 5.8.7 build 815?
by Anonymous Monk on Nov 27, 2009 at 19:27 UTC
    Simply comment out that code.
[reply]
      Simply comment out that code in perl5db.pl.
[reply]

Back to Seekers of Perl Wisdom