Yes the stack trace seems incredibly deep for calling one line of boost code (over 200 depth). I was hoping someone might guess what is going wrong from the structure of the stack trace. I have looked through every frame but can't see anything unusual, but the very fact it is so deep feels wrong. The top-level object being serialized has some structure but is not particularly complicated. Yes it has worked in the past and works for small data sets now. However I did not write the original code and suspect there may be some subtlety which is leading the serializations to blow up in size and I can't find it. Even seemingly small examples give rise to serializations of several megabytes. The stack is of the order of 1Gb and cannot be easily increased but I suspect the stack/heap size just lets it get into such a deep mess before finally dying and the real problem is some conceptual mistake in how my class's serialization has been implemented. Matt -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Frank Birbacher Sent: 22 August 2007 14:18 To: boost-users@lists.boost.org Subject: Re: [Boost-users] boost::serialization throwing bad_alloc Hi! Fletcher, Matthew (Information Technology) schrieb:
I am suffering from boost serialization throwing a bad_alloc exception
at a very low-level that I've been unable to explain or workaround.
I seems strange, right. But have you been successful earlier? That is, is there a point where it started failing? I guess you had smaller programs before which worked. Does it work with less data? Does it work with increased stack size? Sure, a stack overflow should not result in a bad alloc, but just try if nothing else helps. Your stacktrace seems pretty large. Frank _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -- This e-mail is confidential and the information contained in it may be privileged. It should not be read, copied or used by anyone other than the intended recipient. If you have received it in error, please contact the sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and delete the e-mail and do not disclose its contents to any person. We believe, but do not warrant, that this e-mail and any attachments are virus free, but you must take full responsibility for virus checking. Please refer to http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer statement and monitoring policy. Dresdner Kleinwort is the trading name of the investment banking division of Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort Limited, Dresdner Kleinwort Securities Limited and their affiliated or associated companies. Dresdner Bank AG is a company incorporated in Germany with limited liability and registered in England (registered no. FC007638, place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the German Federal Financial Supervisory Authority and by the Financial Services Authority ('FSA') and regulated by the FSA for the conduct of designated business in the UK. Dresdner Kleinwort Limited is a company incorporated in England (registered no. 551334, registered office 30 Gresham Street, London EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort Securities Limited is a company incorporated in England (registered no. 1767419, registered office 30 Gresham Street, London EC2V 7PG), and is authorised and regulated by the FSA.