SIGSEGV after infinite recursion in __vfprintf_chk?

[Yann E. MORIN]

Luca, All,

On Thursday 25 February 2010 18:48:22 Luca Ceresoli wrote:
> I configured CT-NG to build the arm-cortex_a8-linux-gnueabi (glibc)
> toolchain and used it to build:
> - barebox
> - U-boot
> - Linux
> and they work without any problem as far as I could test them.

That's absolutely normal that none has the issue you mention: none of the
above use the C library.

> Sympthom: most programs (but not all) end with a segmentation fault.
> Details follow.
[--SNIP--]
> So I wrote a minimal C program and run it through CT-NG's gdb (which luckily
> does not segfault!), and it seems it infinitely recurses in
> __vfprintf_chk(). SIGSEGV comes immediately after.
[--SNIP--]
> Anybody can suggest in which direction I should investigate?

File a bug against uClibc.

Also, uClibc is on the course to releasing a bug-fix release in the
following days, so this might be interesting to see if they already
fixed that.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



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