Re: "not MAP_STACK" message in dmesg / system message buffer

2020-02-26 Thread Marc Espie
On Tue, Feb 25, 2020 at 08:30:11PM -0500, Andre Smagin wrote: > Hello. > > While prototyping something in C, I made a mistake with > pre-processor macros, which I narrowed down to this: > > int > main() > { > char *test[10][2097152] = { { 0 } }; > } > > Running it results in > $ ./a.out

Re: "not MAP_STACK" message in dmesg / system message buffer

2020-02-25 Thread Theo de Raadt
Theo de Raadt wrote: > Andre Smagin wrote: > > > Hello. > > > > While prototyping something in C, I made a mistake with > > pre-processor macros, which I narrowed down to this: > > > > int > > main() > > { > > char *test[10][2097152] = { { 0 } }; > > } > > > > Running it results in > > $

Re: "not MAP_STACK" message in dmesg / system message buffer

2020-02-25 Thread Theo de Raadt
Andre Smagin wrote: > Hello. > > While prototyping something in C, I made a mistake with > pre-processor macros, which I narrowed down to this: > > int > main() > { > char *test[10][2097152] = { { 0 } }; > } > > Running it results in > $ ./a.out > Segmentation fault (core

"not MAP_STACK" message in dmesg / system message buffer

2020-02-25 Thread Andre Smagin
Hello. While prototyping something in C, I made a mistake with pre-processor macros, which I narrowed down to this: int main() { char *test[10][2097152] = { { 0 } }; } Running it results in $ ./a.out Segmentation fault (core dumped) and it also logs it in dmesg as Feb