I believe I've seen something like this before, it turned out to be some form of wrong binary for the platform it was running on ... or something similar.

I'd suggest you look closely at the SDP you have installed, the *addr2line* binaries, and what "file" has to say about them, and compare that to the platform you're actually trying to run this command, eg on my Linux machine:

$ which ntox86_64-addr2line

.....qnx700/host/linux/x86_64/usr/bin/ntox86_64-addr2line

$ file `which ntox86_64-addr2line`
....qnx700/host/linux/x86_64/usr/bin/ntox86_64-addr2line: symbolic link to x86_64-pc-nto-qnx7.0.0-addr2
line-2.25

$ file `which x86_64-pc-nto-qnx7.0.0-addr2line-2.25`
.....qnx700/host/linux/x86_64/usr/bin/x86_64-pc-nto-qnx7.0.0-addr2line-2.25: ELF 64-bit LSB executable,
x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.72, not st
ripped

if that doesn't prove conclusive, try 'strace ntox86_64-addr2line' (can't tell how to do that on Windows, I'm afraid)

HTH

On Tue, 2018-07-24 at 04:48 -0400, Sai Devasani wrote

Hai Michael Schuster,

My target platform is "x86 64-bit" and am using "ntox86_64-addr2line", but its giving same error.

The command am using is given in below, 

ntox86_64-addr2line -e <binary> <address>



_______________________________________________

OSTech
http://community.qnx.com/sf/go/post118995
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com