[cgiapp] Debugging while using CAP::Dispatch...

[Nic Zero]

 Are you using something like Carp::croak?  If not, the first task is
to work out where you need to put it.  Your first clue is that one of
your errors contains a spelling mistake (occured) so should be easy
to track down via simple text search.  Once you've located your
suspicious code, one approach is to wrap it thus:

require Carp
;eval {
  # suspicious code
  ...
  1
;}
or do {
  Carp::croak(qq{Failed to do something with ... data\n}. $@)
;}


;croak then gives you a stack trace which should give you a clue
about the call chain to be investigated.  Of course you can start
with the exception catcher at your top level and then add similar
to lower levels (repeatedly) till you home-in on where the problem
is.

(If I've misunderstood and you already know this, just ignore all
the above :o) )

Nic

From: B. Estrade <estrabd at gmail.com>
To: CGI Application <cgiapp at lists.openlib.org>
Sent: Thursday, April 19, 2012 at 11:28 pm
Subject: [cgiapp] Debugging while using CAP::Dispatch...

Can't locate object method "error" via package "Can't locate

	object method "error has occured" via package...



Brett