Opened 13 years ago

Closed 13 years ago

#3005 closed Bugs (wontfix)

boost serialization crashes on deserializing, when upgrading from 1.34 to 1.37

Reported by: david.tien@… Owned by: Robert Ramey
Milestone: Boost 1.39.0 Component: serialization
Version: Boost 1.37.0 Severity: Problem
Keywords: Cc:

Description

We recently upgraded from 1.34 to 1.37 and have encountered issues with deserializing existing data.

We get a segfault when trying to reopen the data that was created from the previous release, with this error message in addition to the seg fault: Wind/U Error (130) : Function LocalAlloc, could not allocate memory.

It only occurs on our Linux machines. Windows works fine with the same data. Machine and compiler info:

Red Hat Enterprise Linux WS release 4 (Nahant Update /gcc/gcc-4.1.2-rhel4

The stack trace is attached.

Additional comments:

  1. opening the data in windows, saving, then reopening it on Linux works.

Please advise if there is more information that we can/should provide.

Attachments (1)

pubstack.log (100.6 KB ) - added by david.tien@… 13 years ago.
stack trace

Download all attachments as: .zip

Change History (3)

by david.tien@…, 13 years ago

Attachment: pubstack.log added

stack trace

comment:1 by Robert Ramey, 13 years ago

"Additional comments: 1. opening the data in windows, saving, then reopening it on Linux works."

Looking at this here is an idea.

a) take a file that crashes when loading from linux. b) Loaded it with windows and save it to another file c) Verify that it can now be loaded with linux d) Now diff the two files. This should highlight where the difference is. It will likely show some error in the way the data was serialized for the linux machine in the previous version. e) To verify that the problem has since been fixed, Load the file with linux and save it to a THIRD file. Verify that the Third file is in fact idenitical to the second file.

Robert Ramey

comment:2 by Robert Ramey, 13 years ago

Resolution: wontfix
Status: newclosed

I'm marking this "wont fix" because I don't know what to do about this.

Note: See TracTickets for help on using tickets.