Bug 127275
| Summary: | ldd(1) produces uncatchable output | ||
|---|---|---|---|
| Product: | Base System | Reporter: | kamikaze |
| Component: | amd64 | Assignee: | freebsd-amd64 (Nobody) <amd64> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
This can be closed, because what I thought were two distinct problems has turned out to have the same cause. So this can be considered a duplicate of amd64/127276. Ldd invokes the binary and in case of a nonsensical elf-brand the kernel (at least that is my suspect) posts a message on the terminal. The workaround is to only run ldd on FreeBSD binaries. The safe solution, would in my opinion, be a check weather the binary uses the FreeBSD linker, but this discussion can remain in amd64/127276. State Changed From-To: open->closed See amd64/127276. |
Ldd produces the output 'ELF binary type "0" not known.' upon encountering binaries that are listed as 'Unix - System V' by readelf -e. How-To-Repeat: tcsh: # ldd /usr/local/Adobe/Reader8/ENU/Adobe/HelpViewer/1.0/intellinux/bin/ahv-binary >& /dev/null sh: # ldd /usr/local/Adobe/Reader8/ENU/Adobe/HelpViewer/1.0/intellinux/bin/ahv-binary > /dev/null 2>&1