Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb/testsuite: add simavr.exp board
Date: Sun, 24 May 2020 17:33:04 +0100	[thread overview]
Message-ID: <372695e3-7298-5c84-c009-6e41ca953d9f@redhat.com> (raw)
In-Reply-To: <20200524142040.209234-1-simon.marchi@polymtl.ca>

On 5/24/20 3:20 PM, Simon Marchi via Gdb-patches wrote:
> After sending "target remote :1234" to GDB, I tried using gdb_expect to
> wait for the "Remote debugging using :1234" message and the GDB prompt.
> That didn't work well, but gdb_test_multiple does work.  For example,
> with test gdb.base/break.exp, it blocks at some point when using
> 
>     gdb_expect {
> 	-re "Remote debugging using :1234.*$gdb_prompt " {}
>     }
> 
> If anybody knows how to make gdb_expect work here, I could use it
> (although gdb_test_multiple works fine, except it will probably generate
> a FAIL in cause of failure).

Strange.  gdb_test_multiple is just a wrapper around gdb_expect, so it
should work.  Maybe it's sporadic, and gdb_test_multiple only seems
to work better?  I'd look at RUNTESTFLAGS="-v -v -v --debug" output
to figure out why the pattern didn't match, causing the hang.

Thanks,
Pedro Alves



  parent reply	other threads:[~2020-05-24 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 14:20 Simon Marchi
2020-05-24 14:20 ` [PATCH 2/2] gdb: make avr_integer_to_address generate code or data address based on type Simon Marchi
2020-05-24 16:36   ` Pedro Alves
2020-05-24 16:33 ` Pedro Alves [this message]
2020-05-25 13:29   ` [PATCH 1/2] gdb/testsuite: add simavr.exp board Simon Marchi
2020-05-25 14:44     ` Pedro Alves
2020-05-25 15:57       ` Simon Marchi

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=372695e3-7298-5c84-c009-6e41ca953d9f@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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