You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More of a documentation thing than an issue, I guess, but I spent a lot of time trying to figure out why declaring a new BwTree object on the stack was causing my little test program to coredump. Hope writing up this issue saves someone else a bit of trouble.
Declaring the tree on the heap has no such surprises.
More of a documentation thing than an issue, I guess, but I spent a lot of time trying to figure out why declaring a new BwTree object on the stack was causing my little test program to coredump. Hope writing up this issue saves someone else a bit of trouble.
Declaring the tree on the heap has no such surprises.
Simple little program to demonstrate:
compiling little test with
-Wstack-usage=262144
the compiler reportswarning: stack usage might be 16782800 bytes
and you can observe the dynamic allocation succeeding but not the stack-allocated one.
The text was updated successfully, but these errors were encountered: