Summary: | build failure : undefined reference to __stack_chk_fail | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Serhat Sevki Dincer <mesti_mudam> |
Component: | general | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.2.3 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Serhat Sevki Dincer
2007-04-12 02:18:15 UTC
We've never seen this one before. I couldn't find any mention of __stack_chk_fail in the Valgrind sources. It looks like something that might be used by the C compiler if you had some kind of bounds checking extension like mudflap turned on. Valgrind doesn't link with any external libraries, including libc and libgcc, so any such extension is unlikely to work. Do you know if your C compiler is trying to do something like that? I wonder if the --enable-libstdcxx-debug configure flag to GCC has something to do with it. i just do ./configure --prefix=/some/path make and the make step fails with the above error. i dont give any other option to gcc, and mine is a default install of xubuntu 6.10 (an official variant of ubuntu). i did some googling, and i think it has something to do with -f[no-]stack-protector option of gcc 4.X (it's under "Optimization Options" in the GCC 4.1.2 Manual). i added -fno-stack-protector to a lot of Makefiles, wherever i see "CFLAGS" and it compiled, and ran (dont know if i added to right/appropriate places in the Makefiles, and if the final valgrind works correctly). Possibly fixed on the trunk by r6721. Fixed (trunk r6721, 3_2_BRANCH r6724). |