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>, cel@linux.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Ada compile with -fvar-tracking
Date: Wed, 15 Nov 2023 09:12:11 -0800	[thread overview]
Message-ID: <4a7949f073a8e758f6e7e9591277f2cc9a99de4e.camel@linux.ibm.com> (raw)
In-Reply-To: <87ttpnlzl1.fsf@tromey.com>

Tom:

On Wed, 2023-11-15 at 10:02 -0700, Tom Tromey wrote:
> > > > > > "Carl" == Carl Love <cel@linux.ibm.com> writes:
> 
> Carl> So, per my thoughts last night, I guess I need to dig into the
> expect
> Carl> gdb_compile_ada proceedure and see if I can find something
> there. 
> 
> I've occasionally even hacked logging ("verbose -log" is an easy way)
> into dejagnu code to try to figure out what is going on.  I guess in
> a
> tricky case like this I'd try to find the exact bit of code that's
> deciding the compilation failed.

Yup, my thoughts exactly. It looks to me like there are four commands
that get issued to compile the testcase.  We need to narrow it down to
what command fails and exactly where in the dejagnu code it is issued
from and where the error is "detected".  I haven't debugged dejagnu
code in the past so this could be interesting.  I will look to see
about turning on vebose -log to see what I can get from it.  Thanks for
mentioning that.

                    Carl 



  reply	other threads:[~2023-11-15 17:12 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
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 [this message]
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=4a7949f073a8e758f6e7e9591277f2cc9a99de4e.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