ted.byers has asked for the wisdom of the Perl Monks concerning the following question:
I am trying to resolve a bug in which creation of a div on my web age is incomplete, resulting in two other divs not being created. But, while it is obvious the code that creates these other divs is not executed (although code immediately before this code IS executed), due to an error, no error is written to Apache2's error log (in marked contrast to other coding errors I have fixed).
I tried to get at the problem by having the relevant CGI script open a file, and write diagnostic info to that, but when I access the page after doing that, no such file is created. I do use CGI::Carp::DebugScreen, but it does not get exercised in this bug either.
How do I determine where the problem really is, and the cause of it? I have never before encountered a bug for which none of the usual methods of getting error information produce anything.
Thanks
Ted
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: How to get diagnostic information for a web app when nothing is written to the error log
by Corion (Patriarch) on Oct 15, 2015 at 17:12 UTC | |
|
Re: How to get diagnostic information for a web app when nothing is written to the error log
by fishmonger (Chaplain) on Oct 15, 2015 at 16:47 UTC | |
|
Re: How to get diagnostic information for a web app when nothing is written to the error log
by fishmonger (Chaplain) on Oct 15, 2015 at 17:55 UTC | |
|
Re: How to get diagnostic information for a web app when nothing is written to the error log
by nikosv (Deacon) on Oct 15, 2015 at 18:15 UTC | |
|
Re: How to get diagnostic information for a web app when nothing is written to the error log
by wollmers (Scribe) on Oct 16, 2015 at 09:40 UTC |