Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Carl Love <cel@linux.ibm.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org, cel@linux.ibm.com
Subject: Re: Ada compile with -fvar-tracking
Date: Tue, 14 Nov 2023 13:17:53 -0800	[thread overview]
Message-ID: <fa24824130774c07514686efa55dc19bea4779fa.camel@linux.ibm.com> (raw)
In-Reply-To: <871qcsp1h9.fsf@tromey.com>

Tom:

On Tue, 2023-11-14 at 12:40 -0700, Tom Tromey wrote:
> set flags {debug additional_flags=-cargs additional_flags=-fvar-
> tracking additional_flags=-margs}

So I put that in as follows:

   set flags {debug additional_flags=-cargs additional_flags=-fvar-tracking additional_flags=-margs}

   if {[gdb_compile_ada "${srcfile}" "${binfile} " executable $flags] != ""} {

     return -1
   }

I still get: 

   compilation failed: gcc -c -I./ -fvar-tracking -I/..../testsuite/gdb.ada/finish-large -g -I- 
   /..../testsuite/gdb.ada/finish-large/p.adb

Unfortunately "compilation failed" doesn't tell me much.  So I tried
cutting and pasting each of the compile lines out of the log file and
doing them by hand to see if I could get any more info or figure out
exactly where it fails.  It looks like there are four commands that get
issued:

   gcc -c -I./ -fvar-tracking -I/home/carll/GDB/build-ada/gdb/testsuite/../../../binutils-gdb-ada/gdb/testsuite/gdb.ada/finish-large -g -I- /home/carll/GDB/binutils-gdb-ada/gdb/testsuite/gdb.ada/finish-large/p.adb

   gcc -c -I./ -fvar-tracking -I/home/carll/GDB/build-ada/gdb/testsuite/../../../binutils-gdb-ada/gdb/testsuite/gdb.ada/finish-large -g -I- /home/carll/GDB/binutils-gdb-ada/gdb/testsuite/gdb.ada/finish-large/pck.adb

   gnatbind -I/home/carll/GDB/build-ada/gdb/testsuite/../../../binutils-gdb-ada/gdb/testsuite/gdb.ada/finish-large -x p.ali

   gnatlink p.ali -g -lm -o /home/carll/GDB/build-ada/gdb/testsuite/outputs/gdb.ada/finish-large/p

Well, I can issue each one by hand and don't get any errors.

So then I ran "readelf -wi on /home/carll/GDB/build-
ada/gdb/testsuite/outputs/gdb.ada/finish-large/p.  When I look at the
dwarf output, I see the DW_TAG_call_site tags that are needed and were
not there without the -fvar-tracking stuff. 

So, there is something in the environment or ??? that is causing the
compilation to fail???  It does look like it is theoretically possible
to get Ada to generate the DW_TAG_call_site tags.  Maybe something in
dejagnu?  No clue.  If you have any thoughts or suggestions on
debugging dejagnu that would be great.  

Thanks again.

                          Carl




  reply	other threads:[~2023-11-14 21:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 19:24 Carl Love
2023-11-14 19:40 ` Tom Tromey
2023-11-14 21:17   ` Carl Love [this message]
2023-11-14 22:03     ` Tom Tromey
2023-11-14 22:23       ` Carl Love
2023-11-15 15:04         ` Tom Tromey
2023-11-15 16:42           ` Carl Love
2023-11-15 17:02             ` Tom Tromey
2023-11-15 17:12               ` Carl Love
2023-11-15 17:23                 ` Keith Seitz
2023-11-15 17:29                   ` Carl Love
2023-11-15 22:59                     ` Carl Love
2023-11-16 14:02     ` Luis Machado
2023-11-16 16:11       ` Carl Love
2023-11-16 21:07         ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa24824130774c07514686efa55dc19bea4779fa.camel@linux.ibm.com \
    --to=cel@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox