in reply to perl -d myprog autostarts - but only in one specific directory

Was going to mention the possibility of a .perldb file but that's not showing up in your ls output. The other thing is maybe something is setting PERLDB_OPTS to contain "NonStop=1" in the misbehaving case (perhaps you're sourcing an extra startup file in the one shell you're not in the default case).

The cake is a lie.
The cake is a lie.
The cake is a lie.

Replies are listed 'Best First'.
Re^2: perl -d myprog autostarts - but only in one specific directory
by LanX (Saint) on Jan 18, 2022 at 19:15 UTC
    .perldb can be in home, and ENV could have special settings too.
[reply]

      Right but because things weren't misbehaving in other directories that was suggesting something wonky in a local startup config rather than the global user's. There's also packages (e.g. direnv) which setup environment variables specifically for different directories which could be in play. The con problem found earlier is most likely the culprit but things like this are worth keeping in mind.

      The cake is a lie.
      The cake is a lie.
      The cake is a lie.

[reply]
[d/l]
        Doh ... the "con" bug is really frightening. I've never heard of this DOS feature, and expecting such side effects on Linux wouldn't occur to me.

        Anyway my point was there many ways to tweak/configure the debugger to act differently in different directories. It's even possible to redirect the call to a patched version "perl5db.pl" by changing the environment.

        Cheers Rolf
        (addicted to the Perl Programming Language :)
        Wikisyntax for the Monastery

[reply]

In Section Seekers of Perl Wisdom