December 2014 - Boost - lists.boost.org

[coroutine] x86 msvc11 stack corruption
by Tobias Loew 12 Dec '14

12 Dec '14

Hi, I use Boost 1.55 uni-directional coroutines to build an x86 MSVC11 application. I have a simple pull-type (boost::coroutines::coroutine<void>::pull_type) that under certain reproducable conditions destroys the stack after returning from the coroutine. Here is the corrupted stack as shown by VS2012 > ebs2000.exe!CScriptMainFrame::DoRun(CPascalEditorDoc * 0x00000000, int 0x00000000, int 0x00000000) Line 3372 C++ ebs2000.exe!CScriptMainFrame::OnDebugStepover() Line 4916 C++ mfc110u.dll!_AfxDispatchCmdMsg(CCmdTarget *, unsigned int, int, void (void) *, void *, unsigned int, AFX_CMDHANDLERINFO *) C++ 00000002() Unknown [Frames below may be incorrect and/or missing] mfc110u.dll!CCmdTarget::OnCmdMsg(unsigned int, int 0x00000000, void *, AFX_CMDHANDLERINFO *) Line 364 C++ mfc110u.dll!CWnd::OnCommand(unsigned int 0x00018263, long 0x00000000) Line 2785 C++ mfc110u.dll!CFrameWnd::OnCommand(unsigned int 0x00018263, long 0x00000000) Line 389 C++ ... This only happens in windows x86 32-bit release-builds when the coroutine finishes upon a user-action that also includes a windows WM_SETFOCUS message on my menu-bar. If at least one of the following is true, the stack-corruption does NOT happen: - debug-build - x64 build - using a different pull-type, e.g. enum status_enum{...}; boost::coroutines::coroutine<status_enum>::pull_type - not returning form the coroutine, but pushing just before the end of the coroutine and swapping the pull-type-variable with a default constructed "not-a-coroutine" Even though I have a lot of workarounds, I still would like to know, why this happens. regards Tobias PS: I had to recompile ml /safeseh /c make_i386_ms_pe_masm.asm ml /safeseh /c jump_i386_ms_pe_masm.asm to get SAFESEH-libraries. -- View this message in context: http://boost.2283326.n4.nabble.com/coroutine-x86-msvc11-stack-corruption-tp… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 3

[review] Last day for formal review for Sort library
by Edward Diener 12 Dec '14

12 Dec '14

Today is the last day for the formal review of the Sort library by Steven Ross, which started November 10. We have had some great discussions and reviews so far and I would like to thank everybody involved, but as always we need more formal reviews. If you need any delay for your review after today, please contact me at 'eldiener at tropicsoft dot com' and I will take your review into account if given within a reasonable period of time after today. About the Sort library ================== The Sort library is a library which implements hybrid sorting algorithms based on a Spreadsort ( http://en.wikipedia.org/wiki/Spreadsort ), of which the author of the library, Steven Ross, is the inventor. The algorithm provides a sort that is faster than O(n*log(n)). The library provides a generic implementation of high-speed sorting algorithms that outperform those in the C++ standard in both average and worst case performance. These algorithms only work on random access iterators. They are hybrids using both radix and comparison-based sorting, specialized to sorting common data types, such as integers, floats, and strings. These algorithms are encoded in a generic fashion and accept functors, enabling them to sort any object that can be processed like these basic data types. Where to get it =============== The library is available on github at https://github.com/spreadsort/sort. The library is in modular Boost format and can be cloned to libs/sort under your local modular boost directory. I have provided as the review manager online documentation at: http://eldiener.github.io/sort Review guidelines ================= Reviews should be submitted to the developer list (boost(a)lists.boost.org) preferably with '[sort]' in the subject. Or if you don't wish to for some reason or are not subscribed to the developer list you can send them privately to me at 'eldiener at tropicsoft dot com'. If so, please let me know whether or not you'd like your review to be forwarded to the list. For your review you may wish to consider the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should attempt to answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Even if you do not wish to give a full review any technical comment regarding the library is welcome as part of the review period and will help me as the review manager decide whether the library should be accepted as a Boost library. Any questions about the use of the library are also welcome.

6 11

Help test MSVC 14 CTP compiler
by Andrzej Krzemienski 11 Dec '14

11 Dec '14

Hi Everyone, I am trying to determine the root cause of the failure in one of Boost.Optional regression tests. Namely: http://www.boost.org/development/tests/develop/developer/output/teeks99-08f… Could anyone with the access to MSVC 14 CTP compiler check if the following code compiles? // BEGIN CODE #include <boost/static_assert.hpp> #include <boost/type_traits/is_nothrow_move_assignable.hpp> struct NothrowCtor { NothrowCtor(NothrowCtor&&) BOOST_NOEXCEPT_IF(true) {}; void operator=(NothrowCtor&&) BOOST_NOEXCEPT_IF(false) {}; }; BOOST_STATIC_ASSERT(!::boost::is_nothrow_move_assignable<NothrowCtor>::value); int main() {} // END CODE Regards, &rzej

5 13

Use of boost in safety critical work
by Andrew Marlow 11 Dec '14

11 Dec '14

Hello fellow boosters, I am currently considering a job which involves embedded safety critical. It is for a neonatal ventilator so the safety critical aspect really is critical rather than just 'jolly important'. The company says the development will be in C++ but they have not even heard of boost, let alone use it. They introduced me to a new acronym, well new to me anyway: SOUP. It stands for Software of Unknown Pedigree. They classify boost as SOUP. I have used boost before in embedded work but I have never done safety critical work before so I don't know how widely boost is used there. Can anyone who *has* worked on safety critical stuff comment please? -- Regards, Andrew Marlow http://www.andrewpetermarlow.co.uk

16 26

Re: [boost] [asio] Is Boost.Asio ported for Windows Runtime?
by Moshe Rubin 11 Dec '14

11 Dec '14

Hi Rob, The reason I posted an Asio-related question to this forum is because the Asio mailing list is all but dead. In October there were three (3) posts in all, in November zero posts, and this December only one post - mine. Sounds dead to me. Moshe >> On December 9, 2014 3:11:32 AM EST, Moshe Rubin <moshe(a)hyperlync.com> wrote: >> [snip] >>Can the Boost.Asio maintainer, or anyone else, verify if Boost.Asio can >>be built as-is for WinRT, or does it need to be ported? > I added "[asio]" to the subject to help attract the right audience, but you probably want the Asio mailing list for such a question: http://think-async.com/Asio/MailingList.

2 1

Re: [boost] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Moshe Rubin 11 Dec '14

11 Dec '14

Oliver, I forgot to mention that stack_traits.cpp has a typo: it should include: #include <boost/context/stack_context.hpp> rather than #include <boost/econtext/stack_context.hpp> (note the extra 'e') Moshe -------------------- > > I'm currently attempting to port libraries for Windows Phone 8.1 and have not started concentrating on the units tests (of course. Can you please educate me on how to run the boost.context units tests? > > compile the code in directory <boost>/libs/context/test and execute the binaries on WindowsPhone, please (remove untested.cpp in > build/Jamfile.v2) Oliver, I was able to compile and run the context test as a regular Windows app (i.e., not Windows Phone). Here are the results I got: C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi>test_context.exe Running 9 test cases... f1: entered *** No errors detected Detected memory leaks! Dumping objects -> {478} normal block at 0x00530470, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {477} normal block at 0x00520440, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {473} normal block at 0x0051E3B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {469} normal block at 0x0050E320, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {465} normal block at 0x0050C290, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {461} normal block at 0x0050A200, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {457} normal block at 0x00508170, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {453} normal block at 0x005060E0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {449} normal block at 0x005040B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {445} normal block at 0x00502080, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD Object dump complete. C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi> It is not clear to me how to compile and run the context test on a Windows Phone. Windows Phone does not run regular executables, so a GUI client app would need to be written. It is not clear to me how to run the test for Windows Phone (I doubt the Boost.Test framework supports a Windows Phone interface). Please advise Moshe

1 0

Re: [boost] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Moshe Rubin 11 Dec '14

11 Dec '14

> > I'm currently attempting to port libraries for Windows Phone 8.1 and have not started concentrating on the units tests (of course. Can you please educate me on how to run the boost.context units tests? > > compile the code in directory <boost>/libs/context/test and execute the binaries on WindowsPhone, please (remove untested.cpp in > build/Jamfile.v2) Oliver, I was able to compile and run the context test as a regular Windows app (i.e., not Windows Phone). Here are the results I got: C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi>test_context.exe Running 9 test cases... f1: entered *** No errors detected Detected memory leaks! Dumping objects -> {478} normal block at 0x00530470, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {477} normal block at 0x00520440, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {473} normal block at 0x0051E3B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {469} normal block at 0x0050E320, 65536 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {465} normal block at 0x0050C290, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {461} normal block at 0x0050A200, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {457} normal block at 0x00508170, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {453} normal block at 0x005060E0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {449} normal block at 0x005040B0, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD {445} normal block at 0x00502080, 8192 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD Object dump complete. C:\Private\Dev\3rdParty\Boost\boost_1.57-Port-for-WP81\boost\bin.v2\libs\context\test\test_context.test\msvc-12.0\debug\link-static\threading-multi> It is not clear to me how to compile and run the context test on a Windows Phone. Windows Phone does not run regular executables, so a GUI client app would need to be written. It is not clear to me how to run the test for Windows Phone (I doubt the Boost.Test framework supports a Windows Phone interface). Please advise Moshe

2 1

Re: [boost] Develop Tests Failing Again
by Tom Kent 11 Dec '14

11 Dec '14

On Mon, Dec 8, 2014 at 1:04 PM, Tom Kent <lists(a)teeks99.com> wrote: > It looks like my windows and linux tests have been failing since last > saturday, around 4pm pacific time. > > The end of results/bjam.log is as follows: > boost-test(RUN) "serialization/test_helper_support_xml_warchive" : > "libs/serialization/test/test_ > helper_support.cpp" > error: at D:/local/teeks99-08/a/boost_bb/src/kernel\modules.jam:107 > error: Unable to find file or target named > error: 'test_interrupts.cpp' > error: referred to from project at > error: '../libs/serialization/test' > > Tom > Apparently it is fixed now. Anyone know what happened, I didn't see any messages about it. Tom

2 1

Re: [boost] [Boost-build] Boost 1.57 hot-out-of-Git fails to compile for Windows Phone
by Jürgen Hunold 10 Dec '14

10 Dec '14

Hi Volodya, Am Freitag, 5. Dezember 2014, 11:19:25 schrieb Vladimir Prus: > On 12/04/2014 09:37 PM, Jürgen Hunold wrote: > > Since sometime last week, Boost.Context depends on Boost.System. > > Unfortunately, Boost.Context has to explicitly calculate the > > <address-model> and <architecture> properties in order to select the > > assembler needed, as those properties have no default value (yet). > > It so happens that Boost.System is once requested without those properties > > and a second time with them. And the <layout> rule is asked to build both > > target with the same effective name in stage/lib. => clash. > > > > So explicitly specifying the properties leads to the right solution. > > > > I cross-mail this to the Boost.Build list to see if someone has a > > solution. > > It would seem I'd have to make architecture and address-model always set, > possibly by lifting current boost.context code for same to the top level? > At least I don't see any other plausible soluton. Me neither. And I think this is not the only configuration code that needs uplifting. We have some duplicated configuration code for ICU and zlib. The main difficulty is the question of sensible default feature values for <address-model> and <architecture>. Especially for Windows with its path length limitations. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

1 0

Review request for Compute
by Antony Polukhin 10 Dec '14

10 Dec '14

Hi, Please add the the Compute library to the review schedule. Compute is a GPU/parallel-computing library for C++ based on OpenCL. Author: Kyle Lutz Source code: https://github.com/kylelutz/compute Documentation: http://kylelutz.github.io/compute/ Review Manager: Antony Polukhin Approximate review date: end of November - December 2014 -- Best regards, Antony Polukhin

2 2