From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Clifton To: Freeman.Wang@Marconi.com Cc: binutils@sources.redhat.com Subject: Re: What's the problem of objdump386? Date: Wed, 29 Aug 2001 04:32:00 -0000 Message-id: <200108291234.f7TCYeP12965@bobsleigh.nickc.cambridge.redhat.com> References: <313680C9A886D511A06000204840E1CF6B7ADA@whq-msgusr-02.pit.comms.marconi.com> X-SW-Source: 2001-08/msg00676.html Hi Freeman, : I'm using objdump386(provided with vxWorks 5.4) to disassemble an : image file. But it seems the information it provided was wrong. Since you are using a VxWorks product, you probably ought to contact them directly. They do provide their own support for these tools. : Then I tried to disassemble some object files with it, and found : some of the files were correctly dumped, but most of them are wrong. With a problem like this it is very helpful if you can provide an example of how objdump is failing to disassemble the image. Also it really helps if you can provide a *small* reproducible example of the problem which will let us examine it in detail. : I guess it's because of some kind of offset which I don't : know. Could you tell me what's the problem and is there a newer : version that addresses this problem ? Without more information we cannot diagnose the problem. It is likely however that you do have an old version of the objdump utility. The latest release is version 2.11.2. (Run "objdump386 -v" to find out which version you have). You can download the latest sources and build your own copy by visiting the FSF's FTP site (or one of its mirrors). Cheers Nick