Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#19680 - [valgrind] catching strange errors
Attached to Project:
Arch Linux
Opened by João Rodrigues (gothicknight) - Wednesday, 02 June 2010, 15:52 GMT
Last edited by Allan McRae (Allan) - Thursday, 03 June 2010, 13:20 GMT
Opened by João Rodrigues (gothicknight) - Wednesday, 02 June 2010, 15:52 GMT
Last edited by Allan McRae (Allan) - Thursday, 03 June 2010, 13:20 GMT
|
DetailsDescription:
I'm using valgrind to analyze applications I maintain written in C/C++ build with the latest (core/extra) GCC version. The errors are: ==10108== Jump to the invalid address stated on the next line ==10108== at 0xFFFFFFFFFF600400: ??? ==10108== by 0x4EBAE5C: time (in /lib/libc-2.12.so) ==10108== by 0x4004E6: main (in /home/joao/sandbox/a.out) ==10108== Address 0xffffffffff600400 is not stack'd, malloc'd or (recently) free'd When running the same application under GDB or by simply calling it, there are no errors. I've also installed a new virtual machine with Fedora 13 (x86_64) and recompiled the application and run it through Fedora's valgrind also without any errors. Could this be some issue in the new GCC 4.5 linker or in the valgrind interpreter? Additional info: * package version(s) + valgrind 3.5.0-5 + gcc 4.5.0-4 * config and/or log files etc. + N/A Steps to reproduce: I've created a small application that calls the time() function that crashes in valgrind but runs perfectly anywhere else. |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 03 June 2010, 13:20 GMT
Reason for closing: Fixed
Additional comments about closing: valgrind-3.5.0-6
Thursday, 03 June 2010, 13:20 GMT
Reason for closing: Fixed
Additional comments about closing: valgrind-3.5.0-6
test_valgrind.cpp