[Boost-users] More Granularity in boost::serialization "stream error"?

From: eric (spamsink42_at_[hidden])
Date: 2008-06-10 04:42:26

Hello,

How can I get more detail when boost::serialization raises the
exception "stream error"?

I find that this one error can result from a wide variety of
dissimilar root causes, but regardless of the nature of the problem
(or the size of the buffer) the only information provided by
boost::serialization is that one opaque string.  It is easy to lose a
lot of time tracking down the problem.

I have worked with other more traditional XML parsers that raise
exceptions in the form "Unexpected character in line x column y."  I
am aware that the architecture of boost::serialization is completely
different to that of a traditional XML parser but the bottom line is
the same, if I could get more granularity on this exception it would
save a lot of time troubleshooting.

Debugging seems not to be an option as my debugger (gdb) gets lost in
boost header files and templates.  I am left with trial and error,
chopping up the stream into smaller pieces until I can isolate the
invalid content.

Any ideas?

Thanks,
Eric