Shouldn't Dancer's error traceback include the user code? i put the request into the bug tracker long ago, but no comments. Do you see a technical reason for not show user code too? (i dont, and in my non-dancer code it works that way).
Niels L On Mon, 2013-06-03 at 20:10 +0100, David Precious wrote: > On Mon, 03 Jun 2013 20:01:43 +0100 > gvim <[email protected]> wrote: > > > On 03/06/2013 19:57, David Precious wrote: > > > > > I see nothing in the code above that could raise the error you are > > > seeing, so I suspect the problem lies within Astro::Register::run(). > > > > > > > > That's the problem. Astro::Register in turn uses other custom modules > > but Dancer doesn't seem to be able to reveal the details of the > > binding error. I would have to send you the code for the whole > > application, which isn't realistic. > > Well, I've at least pointed at the likely cause. > > You could try running your app under Carp::Always to make warn/die > provide stack traces, e.g. > > perl -MCarp::Always bin/app.pl > > That might help. > > Of course, it's not helpful if Dancer isn't giving you a stack trace > with show_errors on - I'll see if I can reproduce that. > > > _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
