Spam:**********, Re: objcopy problems

X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information 
X-SpamDetect: **********: 10.400001 From3consonants=0.3, Share Market Scam=2.0, SPF Soft=3.0, DodgySource=2.0, SPF Default Fail=2.5, X-Verify-SMTP present=0.6
X-SpamDetect-Info: ------------- End ASpam results -----------------

Jaysen Roper wrote:
> I am having problems with m68k-coff-objcopy.exe
> 
> Whenever I enable “—debugging†it crashes with the following error…
> 
> m68k-coff-objcopy --debugging -O ieee -R .id -R .system demo.bin demo.695
> [main] C:\heber\exe\gcc-m68k\bin\m68k-coff-objcopy.exe 1030 (0) 
> handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
> [main] m68k-coff-objcopy 1030 (0) handle_exceptions: Dumping stack trace 
> to m68k-coff-objcopy.exe.core
> make: *** [demo.695] Error 11
> 
> I am using David Fiddes excellent GCC-M68K v6 (1998) with no other nix 
> tools in the mix.
> 
> Davids tools are based on EGCS-1.1.2 and GNU Binutils-2.9.1
> 
> I have pulled 5 projects out of our archive, and sure enough, this 
> happens on all builds (none of them had –debugging enabled)
> 
> I have tried objcopy with ieee / srec / tekhex / ihex / binary. All give 
> the same error at the same point.
> 
> Ieee is our preferred format because it is the preferred format of our 
> new IDE/DBG system.
> 
> Is there a reliable way of converting our coff files to ieee?
> 

The coff format is not used that much these days with the m68k target. I think 
all are ELF.

I suggest you take a look at the Codesourcery tools available for download 
from their web site. Install those tools and see how the objcopy in their 
package goes. It may not crash.

Regards
Chris
---
[email protected]              Send a post to the list.
[email protected]        Join the list.
[email protected]    Join the list in digest mode.
[email protected]     Leave the list.