Hi Luigi,
thank you for your help, I have updated the settings as you suggested but the problem still remain... Now the output debug is longer than before, I attached 2 txt files (both are safe): 1 file contains the whole list of debug output before the system crash, maybe you can find some useful info. 2 file contains the crash message from Matlab Let me know if you can't open them. (I dont know if this can help you but now, my MS VC++ (2005) doesnt crash. It crashes only Matlab). Thanks in advance Paolo >----Messaggio originale---- >Da: [hidden email] >Data: 09/08/2010 10.58 >A: "[hidden email]"<[hidden email]> >Cc: <[hidden email]>, <[hidden email]> >Ogg: Re: R: Re: [Quantlib-users] R: Re: Curve building with depo, futures and swaps > >On Fri, 2010-08-06 at 08:29 +0200, [hidden email] wrote: >> well the try/catch I used look like this >> >> try { >> ...... (code) >> >> } catch (std::exception& e) { >> std::cerr << e.what() << std::endl; >> } catch (...) { >> std::cerr << "unknown error" << std::endl; >> } >> >> I get the expections if I use swaps > >Does it run > std::cerr << e.what() << std::endl; >in that case? If so, what does it print? > >> In all these cases, the following message is the debug output (which it >> a problem coming from the link between MATLAB and Microsoft VS): >> First-chance exception at 0x053ec94c in MATLAB.exe: 0xC0000005: Access >> violation reading location 0x00000004. > >This looks more like an out-of-bounds access or something like it. To >get some more information, you might try recompiling with some updated >settings, as suggested in ><http://sourceforge.net/mailarchive/forum.php? com&forum_name=quantlib-dev>. > >Later, > Luigi > > >-- > >Newton's Law of Gravitation: >What goes up must come down. But don't expect it to come down >where you can find it. Murphy's Law applies to Newton's. > > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ QuantLib-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-users |
On Tue, 2010-08-10 at 09:07 +0200, [hidden email] wrote:
> I have updated the settings as you suggested but the problem still remain... > Now the output debug is longer than before, I attached 2 txt files (both are > safe): > 1 file contains the whole list of debug output before the system crash, maybe > you can find some useful info. > 2 file contains the crash message from Matlab The problem is, neither of them contains something showing that the exception was caught. If you did put } catch (std::exception& e) { std::cerr << e.what() << std::endl; } catch (...) { std::cerr << "unknown error" << std::endl; } in your code, there should be something printed. If if was a QuantLib::Error, it might contain information about what goes wrong. Are you sure you have the above? Maybe you can modify to something like } catch (std::exception& e) { std::cerr << " ****** " << e.what() << std::endl; } catch (...) { std::cerr << " ****** unknown error" << std::endl; } to make it easier to look for the ****** in the output? Luigi > (I dont know if this can help you but now, my MS VC++ (2005) doesnt crash. It > crashes only Matlab). > > Thanks in advance > Paolo > > > >----Messaggio originale---- > >Da: [hidden email] > >Data: 09/08/2010 10.58 > >A: "[hidden email]"<[hidden email]> > >Cc: <[hidden email]>, <[hidden email]> > >Ogg: Re: R: Re: [Quantlib-users] R: Re: Curve building with depo, futures > and swaps > > > >On Fri, 2010-08-06 at 08:29 +0200, [hidden email] wrote: > >> well the try/catch I used look like this > >> > >> try { > >> ...... (code) > >> > >> } catch (std::exception& e) { > >> std::cerr << e.what() << std::endl; > >> } catch (...) { > >> std::cerr << "unknown error" << std::endl; > >> } > >> > >> I get the expections if I use swaps > > > >Does it run > > std::cerr << e.what() << std::endl; > >in that case? If so, what does it print? > > > >> In all these cases, the following message is the debug output (which it > looks > >> a problem coming from the link between MATLAB and Microsoft VS): > >> First-chance exception at 0x053ec94c in MATLAB.exe: 0xC0000005: Access > >> violation reading location 0x00000004. > > > >This looks more like an out-of-bounds access or something like it. To > >get some more information, you might try recompiling with some updated > >settings, as suggested in > ><http://sourceforge.net/mailarchive/forum.php? > thread_name=AANLkTimm4AA_Vbi5elHT2H9u5oWRwzKJUKR65sqEPtXe%40mail.gmail. > com&forum_name=quantlib-dev>. > > > >Later, > > Luigi > > > > > >-- > > > >Newton's Law of Gravitation: > >What goes up must come down. But don't expect it to come down > >where you can find it. Murphy's Law applies to Newton's. > > > > > > > -- Westheimer's Discovery: A couple of months in the laboratory can frequently save a couple of hours in the library. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ QuantLib-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-users |
Free forum by Nabble | Edit this page |