Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] inadvertent language switch during breakpoint_re_set_one
Date: Thu, 10 May 2018 19:08:00 -0000	[thread overview]
Message-ID: <dfdb440b-b8ad-dc4d-b06d-4dbbf9d35627@redhat.com> (raw)
In-Reply-To: <1525976353-67414-1-git-send-email-brobecker@adacore.com>

Hi, Joel,

Just a quick question:

On 05/10/2018 11:19 AM, Joel Brobecker wrote:
> gdb/testsuite/ChangeLog:
> 
>         * gdb.ada/bp_fun_addr: New testcase.

Is this test supposed to trigger the failure? It passes for me:

$ make check TESTS=gdb.ada/bp_fun_addr.exp
[snip]
		=== gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/keiths/work/gdb/branches/virgin/linux/gdb/testsuite/../../../src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running /home/keiths/work/gdb/branches/virgin/linux/gdb/testsuite/../../../src/gdb/testsuite/gdb.ada/bp_fun_addr.exp ...

		=== gdb Summary ===

# of expected passes		3

Is my environment different from yours, i.e., is this something that is exposed on your internal tree?

Keith


  parent reply	other threads:[~2018-05-10 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 18:42 Joel Brobecker
2018-05-10 18:58 ` Sergio Durigan Junior
2018-05-10 19:26   ` Joel Brobecker
2018-05-10 19:08 ` Keith Seitz [this message]
2018-05-10 19:21   ` Joel Brobecker
2018-05-10 19:35     ` Keith Seitz
2018-05-10 19:29 ` Tom Tromey
2018-05-10 20:59   ` Joel Brobecker
2018-05-31  0:02     ` Joel Brobecker
2018-06-01 12:42     ` Pedro Alves
2018-06-01 16:39       ` Joel Brobecker

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=dfdb440b-b8ad-dc4d-b06d-4dbbf9d35627@redhat.com \
    --to=keiths@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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