Re: [Cppcms-users] Advice on debugging file upload

[<ele...@ex...>]

I've been following this discussion and I ran the same test on FreeBSD 8
and it only prints "My Error", but no trace.

Petr

>>~/src/cppcms-1.0.1/mybuild$ ./a.out 
>>My Error
>>0x107963102: booster::backtrace::backtrace(unsigned long) + 0x76 in
>> /Users/douglivesey/src/cppcms-1.0.1/mybuild/./a.out
>>0x1079632c9: booster::runtime_error::runtime_error(std::string const&) +
>> 0x39 in /Users/douglivesey/src/cppcms-1.0.1/mybuild/./a.out
>>0x107962eda: foo() + 0x4a in
>> /Users/douglivesey/src/cppcms-1.0.1/mybuild/./a.out
>>0x107962f4a: bar() + 0x9 in
>> /Users/douglivesey/src/cppcms-1.0.1/mybuild/./a.out
>>0x107962f5d: main + 0xe in
>> /Users/douglivesey/src/cppcms-1.0.1/mybuild/./a.out
>>0x107962e88: start + 0x34 in
>> /Users/douglivesey/src/cppcms-1.0.1/mybuild/./a.out
>
>
> Ok, the stack backtrace works on Mac OS X.
>
>
> If so you should probably see where exactly the exception comes from in
> the
> log - including cppcms::widgers::file::value() in the stack trace.
>
> Use it, it is very powerful tool.
>
> (Don't forget -dynamic options)
>
> Artyom
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users
>