Hi Juan Cespedes,
Was learning ltrace, tried a few bugs on the debian bugs list.
#614994 [n| | ] [ltrace] ltrace: Doesn't understand scripts with #!
lines
==========================================================================
/tmp$ cat x
#!/bin/sh
echo Hello
/tmp$ ./x
Hello
/tmp$ strace -f -o /dev/null ./x
Hello
/tmp$ ltrace -f -o /dev/null ./x
ltrace: Can't open ELF file "./x"
- Josh Triplett
==========================================================================
The above is the snippet from the bug report log.
If bash script is run like "./script_name" only bash is understands and
starts interpreting it as a script.
other-wise the filesystem see's it as a collection of ASCII text.
$ file x
x: ASCII text
And from the source code,
===============
if (lte->elf == NULL || elf_kind(lte->elf) != ELF_K_ELF)
/* is true*/
error(EXIT_FAILURE, 0, "Can't open ELF file \"%s\"", filename);
===============
But if the program is run like this below, it works fine.
$ ltrace -f -o /dev/null bash x
$ ltrace -f -o /dev/null sh x
Guess this is a wrong bug report filed
#606026 [i| | ] [ltrace] handle_event.c:565: handle_breakpoint:
Assertion `sbp' failed.
==========================================================================
This bug is not reproducible with the latest changes. But not closed
yet. Verified it with the following packages.
ii libc6:amd64 2.17-97 amd64 Embedded GNU C Library:
Shared li
ii ltrace 0.5.3-2.1 amd64 Tracks runtime library
calls in d
ii libelfg0-dev 0.8.13-5 amd64 an ELF object file access
library
M still a student, mistakes are possible in whatever mentioned above.
Will learn from them, and Hope this helps.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
