[Bug libstdc++/63614] With gcc-4.8.3 and -stdgnu++0x call to std::this_thread::get_id() creates SIGSEV

dyle at dyle dot org gcc-bugzilla@gcc.gnu.org
Tue Nov 4 11:00:00 GMT 2014


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63614

Oliver Maurhart <dyle at dyle dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from Oliver Maurhart <dyle at dyle dot org> ---
Thank you for the hint. 

Using valgrind gave me the warning of "switching stacks?", which let me
increase my stack-size, which wasn't enough, which gave me the final clue, that
my last changes exploded the stack with way too great local variables arrays.

Re reconfigured my code to create dynamic arrays as local vars like

    std::unqiue_ptr<uint64_t[]> d(new uint64_t[REAL_LARGE_NUMBER_HERE]);

instead of just

    uint64_t d[REAL_LARGE_NUMBER_HERE];

Now my stack feels fine again.

Thx.

Solved - invalid.



More information about the Gcc-bugs mailing list