[Iostreams] Known issue with 32-bit and iostreams::file_descriptor_sink?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Iostreams] Known issue with 32-bit and iostreams::file_descriptor_sink?

Boost - Users mailing list
Hi,

I'm trying to debug several issues in ledger
(https://www.ledger-cli.org/) under Fedora 26 (boost 1.63;
https://github.com/ledger/ledger/issues/534) and Debian
Stretch (boost 1.62;
https://github.com/ledger/ledger/issues/539).

These issues occur only on 32-bit architectures (i386/i686),
and on Fedora 26 (boost 1.63) some segmentation faults can
be /fixed/ by executing:

| std::ostream *dummy = new iostreams::stream<iostreams::file_descriptor_sink>(2, iostreams::never_close_handle);

but this does not "work" on Debian Stretch (boost 1.62).

Does that ring a bell for anyone?  (NB: I don't want to im-
ply that there is a bug in Boost, but maybe someone recog-
nizes the scenario and can suggest where the real issues
probably lie.)

TIA,
Tim
_______________________________________________
Boost-users mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|

Re: [Iostreams] Known issue with 32-bit and iostreams::file_descriptor_sink?

Boost - Users mailing list
I wrote:

> […]

> These issues occur only on 32-bit architectures (i386/i686),
> and on Fedora 26 (boost 1.63) some segmentation faults can
> be /fixed/ by executing:

> | std::ostream *dummy = new iostreams::stream<iostreams::file_descriptor_sink>(2, iostreams::never_close_handle);

> but this does not "work" on Debian Stretch (boost 1.62).

> […]

The same effect could be achieved by "malloc(208)", i. e.
iostreams::file_descriptor_sink has no influence on the is-
sue.

Sorry for the noise,
Tim
_______________________________________________
Boost-users mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-users