Re: SIGSEGV after infinite recursion in __vfprintf_chk?

["Luca Ceresoli" <list at lucaceresoli dot net>]

> > Basically, __vfprintf_chk is called in place of vfprintf. That's a linker
> > trick, where vfprintf is in fact an alias to __vfprintf_chk. Its purpose
> > is to check for stack overflow (I don't dare look at how it does so).
> 
> What puzzles me is the fact that __vfprintf_chk() does not (seem to) detect
> any problem, instead it is apparently recursing indefinitely until there's
> no more RAM available (see the ook_killer and the end of my gdb log).

A quick update.

I tried to re-run my ct-NG tollchain with different versions of
binutils, glibc, gcc, kernel headers etc but without any difference.

My test program compiled with CodeSourcery
(http://www.codesourcery.com/sgpp/lite/arm/portal/release1039)
does work.
It does never enter __vfprintf_chk().

Luca



--
For unsubscribe information see http://sourceware.org/lists.html#faq