Closed brycelelbach closed 12 years ago
[comment by blelbach] [Trac time Tue Feb 28 06:32:34 2012] This turned out to be a slicing issue (e.g., we were copying std::exception implicitly with boost::current_exception).
[comment by blelbach] [Trac time Tue Feb 28 13:33:51 2012] r7199
[reported by blelbach] [Trac time Fri Feb 3 20:27:43 2012] ||2f6ef8319fd3192da671f9eca9d4da96253866b9, Boost 1.47.0, GCC 4.6.2, debug
This issue can be reproduced by running neutron star in distributed, with the following options:
Locality 1:
Locality 2:
A parcel de-serialization error occurs, however the exception reported on stderr is incorrect (the what message only says "std::exception").
Locality 1 stdout/stderr:
Locality 2 stdout/stderr:
Notice the difference in exception reports on both localities.
Correct exception message in logs:
The logs lead me to believe that report_exception_and_terminate might be the culprit, but I haven't investigated this.
Initially I thought this was an exception serialization problem, but I believe I have patched the issue there (75b130c6a79130488d1dc0a41ea1df2a533378a7) and this bug still occurs. The logs reveal the correct what message.