Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - What's wrong with these ARM binary?: (3 Items)
   
What's wrong with these ARM binary?  
IDE 4.5, very simple QNX C project, compiled (for a test) for all platforms, release and debug.

Release binary has 'play' icon.
Debug binary has 'bug' icon.

However, in this case, the ARM release binary has the 'bug' icon. Even more strange, when hitting the little +, the 
contents look pretty odd ('lib1funcs.asm' is in there only, but this twice). Other binaries have much more content (e.g.
 function names are visible).

I currently don't have an ARM platform so I can't test if the binary actually works.

What is wrong here? 


- Malte
Attachment: Image strange_contents_of_arm_binary.JPG 170.8 KB
Re: What's wrong with these ARM binary?  
Pr this please. Something wrong with either binary parser or debug symbols.

Malte Mundt wrote:
> IDE 4.5, very simple QNX C project, compiled (for a test) for all platforms, release and debug.
> 
> Release binary has 'play' icon.
> Debug binary has 'bug' icon.
> 
> However, in this case, the ARM release binary has the 'bug' icon. Even more strange, when hitting the little +, the 
contents look pretty odd ('lib1funcs.asm' is in there only, but this twice). Other binaries have much more content (e.g.
 function names are visible).
> 
> I currently don't have an ARM platform so I can't test if the binary actually works.
> 
> What is wrong here? 
> 
> 
> - Malte
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post17526
> 
> 
> ------------------------------------------------------------------------
> 
Re: What's wrong with these ARM binary?  
Hm, there are 36 PR's from me still non-closed, shall I really file another one? Can't we have the existing ones fixed 
first? ;-)

Anyway, I filed PR #63463 on this.


- Malte