Opened 14 years ago
Closed 12 years ago
#2942 closed Bugs (wontfix)
32 bit build of Interprocess managed_shared_memory fails on 64 bit machine
| Reported by: | Owned by: | Ion Gaztañaga | |
|---|---|---|---|
| Milestone: | Boost 1.39.0 | Component: | interprocess |
| Version: | Boost 1.38.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
I have a 32 bit build (Linux) of my application that uses a managed_shared_memory. I follow very closely to the examples on the "Quick Guide for the Impatient" page. However, when I run the binary on some 64 bit machines (Linux), it intermittently fails to open a previously existing shared memory object, throwing an exception that claims "Value too large for specified format." I debugged it in gdb, and found that the ::fstat command in function get_file_size in boost/interpocess/detail/os_file_functions.hpp was getting an error, with the specified error string. I have the strong suspicion that it is a matter of a 64 bit machine misinterpreting the input parameter from a 32 bit call. I am running on a SUSE 9 based Linux distribution in x86_64 mode in a 2.6.X kernel.
Couldn't reproduce the problem. Please reopen if new there are new details.