what I wrote still applies - qnx is POSIX-compliant after all :-)
$ which ntox86_64-addr2line
/usr/bin/ntox86_64-addr2line
$ file `which ntox86_64-addr2line`
/usr/bin/ntox86_64-addr2line: symbolic link to x86_64-pc-nto-qnx7.0.0-addr2line-2.25
$ file `which x86_64-pc-nto-qnx7.0.0-addr2line-2.25`
/usr/bin/x86_64-pc-nto-qnx7.0.0-addr2line-2.25: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically
linked, interpreter /usr/lib/ldqnx-64.so.2, 0 bytes lazy stack, 4096 bytes preallocated stack, BuildID[md5/uuid]=1
dbfa62b31ec82d74b928b4c820727d2, not stripped
$ ntox86_64-addr2line
ntox86_64-addr2line: 'a.out': No such file
On Tue, 2018-07-24 at 05:38 -0400, Sai Devasani wrote:
Actually am trying to build a utility on target, that can fetch the details from core dump.
I am executing "ntox86_64-addr2line" command on target itself.
_______________________________________________
OSTech
http://community.qnx.com/sf/go/post118997
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com