2009/5/9 Andrii Arsirii <[email protected]>:
> Hi all.
>
> From this snippet:
>
> Wt::WApplication *createApplication(const Wt::WEnvironment& env)
> {
> Wt::WApplication* app = new Application(env);
> return app;
> }
>
>
Would this solve your problem:
Wt::WApplication *createApplication(const Wt::WEnvironment& env)
{
try {
Wt::WApplication* app = new Application(env);
} catch (...) {
abort();
}
return app;
}
Or, in case that it does not happen during construction, do the same
trick but in WApplication::notify. I'm not sure that this will still
give you your stack trace, though... Would it be possible to set a
breakpoint on the exception's constructor?
The main reason that all exceptions are caught there is because we do
not want that an uncaught exception from one session terminates the
entire application (and therefore all sessions), but I understand that
you sometimes want that behaviour during development.
Best regards,
Wim.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
