public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR17525 - breakpoint commands not executed when program run, from -x script
Date: Wed, 14 Jan 2015 11:29:00 -0000	[thread overview]
Message-ID: <20150114112942.GK8167@adacore.com> (raw)
In-Reply-To: <54B56B60.6040406@redhat.com>

Hi Pedro,

> gdb/
> 2015-01-12  Pedro Alves  <palves@redhat.com>
> 
> 	PR gdb/17525
> 	* breakpoint.c: Include "interps.h".
> 	(bpstat_do_actions_1): Also check whether the interpreter is
> 	async.
> 
> gdb/testsuite/
> 2015-01-12  Pedro Alves  <palves@redhat.com>
> 	    Joel Brobecker  <brobecker@adacore.com>
> 
> 	PR gdb/17525
> 	* gdb.base/bp-cmds-execution-x-script.c: New file.
> 	* gdb.base/bp-cmds-execution-x-script.exp: New file.
> 	* gdb.base/bp-cmds-execution-x-script.gdb: New file.

Many many thanks for the fix.

I completely missed the fact that we were running in non-async
mode, and now I am slapping the front of my head yelling a "duh!".
I learnt something from your help, so thank you. And the bonus
is that the fix looks fairly simple, which is good, because...

... this is an issue which was identified as a regression for
7.8 and 7.9. I suggest we backport them to both branches, if
you agree, and once the patch is pushed to master, I volunteer
doing so if that saves you a bit of time.

Regarding GDBFLAGS, I'm wondering whether this might be one of
those globals that we should be restoring at the start of each
testcase (via gdb_init)...

-- 
Joel

  reply	other threads:[~2015-01-14 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 19:00 Pedro Alves
2015-01-14 11:29 ` Joel Brobecker [this message]
2015-01-14 13:27   ` Pedro Alves

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=20150114112942.GK8167@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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).