public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@linux.ibm.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Ada compile with -fvar-tracking
Date: Wed, 15 Nov 2023 09:29:12 -0800	[thread overview]
Message-ID: <6eed52fac162f4082974fb71580a938059bdc4ef.camel@linux.ibm.com> (raw)
In-Reply-To: <4a88dca4-1020-461a-ad7a-616541e58064@redhat.com>

Keth:

On Wed, 2023-11-15 at 09:23 -0800, Keith Seitz wrote:
> When it comes to debugging what expect is up to, if you can narrow
> the problem(s) to a proc or small area of commands,  you can
> surround 
> that bit of code with "exp_internal 1" and "exp_internal 0". This
> will 
> cause expect to output all of its pattern-matching data: buffer 
> contents, attempted matches, actual matches, etc.
> 
> [You can also globally turn on exp_internal by passing a verbosity
> level of 2+ to dejagnu. That will output "dbg.log" with ALL expect
> pattern matching logging. Far too verbose (usually) to be useful.]

Thanks!!  I think that will be very helpful to be able to fine tune the
debugging.

                  Carl 


  reply	other threads:[~2023-11-15 17:29 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
2023-11-15 17:23                 ` Keith Seitz
2023-11-15 17:29                   ` Carl Love [this message]
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=6eed52fac162f4082974fb71580a938059bdc4ef.camel@linux.ibm.com \
    --to=cel@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).