From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,df1a7f1c3c3bc77e X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!out04b.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!in04.usenetserver.com!news.usenetserver.com!news-in-02.newsfeed.easynews.com!easynews.com!easynews!news.he.net!xara.net!gxn.net!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: GNAT Professional machine code listings Date: Sun, 06 May 2007 15:50:23 +0100 Organization: Pushface Message-ID: References: NNTP-Posting-Host: pogner.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.demon.co.uk 1178463023 17758 62.49.19.209 (6 May 2007 14:50:23 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Sun, 6 May 2007 14:50:23 +0000 (UTC) Cancel-Lock: sha1:UFvXcMKR2ru4cY8qRly5O41TB6w= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (darwin) Xref: g2news1.google.com comp.lang.ada:15597 Date: 2007-05-06T15:50:23+01:00 List-Id: Kilgallen@SpamCop.net (Larry Kilgallen) writes: > The last I read in this newsgroup. ACT was inexorably opposed to the > generation of machine code listing files. For us this makes their > offering a non-starter. We need to be able to have a customer for > our commercial product send back a stack dump from a production > release of the software. Then we need to be able to use that > information to see exactly which instruction went south. That makes > GNAT Pro a non-starter as I see it. A colleague in a similar situation (and more used to deep tracing than I've had to be) had a lot of success using a disassembly (via objdump, I think) of a GNAT powerpc-wrs-vxworks executable. The code we supply is stripped (objcopy --strip-debug, I think) but so long as we keep the unstripped executable all is well! His problem was to determine exactly which component of a record assignment was causing the Constraint_Error. But in any case you have always been able to generate machine code listings using the -S flag. OK, the .s files end up in the library where the .o files would normally go, which can be confusing! (this is with GNAT 3.16a1, don't know what later versions do).