| Anonymous | Login | Signup for a new account | 11-10-2008 10:59 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000794 | [BusyBox] Other | minor | always | 03-21-06 15:56 | 02-14-08 09:11 | ||||
| Reporter | wmb | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 1.01 | ||||||
| Summary | 0000794: ldd fails with ash - "set -o" doesn't return nonzero exit status [PATCH attached] | ||||||||
| Description |
The "ldd" command is a shell script. (At least some versions of ...) the script include the line: if set -o pipefail 2> /dev/null; then The intention is to test for the existence of the pipefail option. When the busybox version of ash is used as /bin/sh, this line causes the script to exit, instead of "set -o pipefile" returning nonzero exit status and letting "if" do its thing. The net result is that "ldd" silently exits, instead of doing its job of displaying library dependencies. A patch to fix this is attached. The patch changes the behavior of the "set" command so that instead of bailing out if presented with an unrecognized argument to "-o", it returns exit status 1 (the same as bash). The patch is against the version of ash in Busybox 1.1.0 |
||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |