I'm delighted of the feedback. Thanks. It's not my main activity but I'm investigating this topic by a while. Now I found some workaround (fixing #line) so that I can have a quite effective remote debugging session. But I'm interested to fix it definitely and understand the problem. Besides starting to add a first question on this site ( here ), I then provided a more detailed question here but I got no solution.

I'm just trying to use 2 old (and I so guess stable-enough) modules, mod_perl and Apache::DB. Even developed by the same author, Doug MacEachern, so I believe they should understand each other. I'm running them out of the box. MY code is only the 4 lines snipped shown, just to see them working as expected for the most simple case.

So the lab is this:

1. have Apache and mod_perl

2. have module Apache::DB

3. use the most simple httpd.conf. Mine is this

4. excute Apache in not-forking mode httpd  -X -DPERLDB -f simple.httpd.conf

5. point your browser to your snippet

6. go to your new fresh debug prompt, arisen magically in the shell of point 4

7. step-step-step-step ... till reaching the sub default_handler of mod_perl

(all will happen inside mod_perl, the file ModPerl::RegistryCooker ) 
       A) sub default_handler {
          |
       B) |___| $rc = $self->convert_script_to_compiled_handler;
              |       |
              |       |___|  ....
       C)     |           | my $line = $self->get_mark_line;
       D)     |           | my $eval = join '' .....   <------ the joi
+n shown in my opening question above
       E)     |           | $rc = $self->compile(\$eval);
              |           |              |__
              |           |                 | ....
       F)     |           |                 |  eval $$eval;  <----- tr
+anslated in   return $self->error_check;
              |           |                 |
              |           |
       G)     |           | $self->cache_it;
              |
       H)     | $rc = $self->run;
              |              | ....
       I)     |              | eval { $cv->($r, @_) };  ------->   JUM
+P INTO USER CODE  (here #line will not be understood)

[download]
I much appreciate the work of sir MacEachern, as it's a complex matter, but it shouldn't be such a pain to turn them on, after having simplifed your code to 4 lines (shebang, and print CGI header included!, ... so 2 lines). Why that #line is so difficult to understand ? Moreover as already linked (here again) , I found some different opinion on how it should be used so the fixed #line 1 in mod_perl code is on a different choice..... that incidentally does not work so well :)

In reply to Re^2: right usage of #line ?? by jjmoka
in thread right usage of #line ?? by jjmoka

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.