Summary: | sys-libs/glibc-2.6.1: bus error in ld-linux-x86-64.so.2 when used as executable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eric Lesage <erl-dev> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Stack trace
readelf output of example affected file |
Description
Eric Lesage
2007-11-12 08:17:32 UTC
Created attachment 135806 [details]
Stack trace
GDB session: stack trace
.debug files are not ELFs ... i dont know why you expect the ldso to handle them Hello, I don't expect a program just to core dump when analysing an input, even if the input is not what it expects. In case it's not clear, I don't want it to run the file (of course it can't), hence the "--verify" parameter. The usual behavior of the loader when verifying a non-ELF file is to return with code 1. When an invalid ELF file (eg. static) is given, it usually returns with code 2. Created attachment 135810 [details]
readelf output of example affected file
Hello again,
Upon inspection, .so.debug files are proper ELF files, at least according to readelf. Perhaps something is wrong with some of them, I cannot say...
This was done with:
$ readelf -a /usr/lib/debug/usr/lib64/libedc_ecc.so.1.0.debug
they are not proper ELFs ... readelf can just sometimes construct something somewhat meaningful out of the input what you want are sanity checks in the ldso to verify the ELF being parsed is valid ... that is not a good idea as all the sanity checks needed will simply slow down the entire system at no benefit whether you get a message "bus error" or "segfault" or the ldso detects the error and tells you "invalid ELF", it's all the same: it wont work |