From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [commit/obvious] Add "volatile" keyword to "struct gdb_exception" declaration
Date: Fri, 17 Jan 2014 21:50:00 -0000 [thread overview]
Message-ID: <m3y52e5ld7.fsf@redhat.com> (raw)
In-Reply-To: <m361pi709i.fsf@redhat.com> (Sergio Durigan Junior's message of "Fri, 17 Jan 2014 19:43:05 -0200")
On Friday, January 17 2014, I wrote:
> Author: Sergio Durigan Junior <sergiodj@redhat.com>
> Date: Fri Jan 17 19:39:57 2014 -0200
>
> Add "volatile" keyword to "struct gdb_exception" declaration
>
> While doing something else, I found that those 2 places were incorrectly
> declaring a "struct gdb_exception" without using the "volatile" keyword.
> This commit fixes that.
>
> 2014-01-17 Sergio Durigan Junior <sergiodj@redhat.com>
>
> * breakpoint.c (insert_bp_location): Add "volatile" keyword to "struct
> gdb_exception" declaration.
> * remote.c (getpkt_or_notif_sane): Likewise.
Ops, Joel, sorry that I forgot to add the "gdb/" path before the
ChangeLog in the commit message. I'll try harder to remember next
time...
--
Sergio
prev parent reply other threads:[~2014-01-17 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 21:43 Sergio Durigan Junior
2014-01-17 21:50 ` Sergio Durigan Junior [this message]
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=m3y52e5ld7.fsf@redhat.com \
--to=sergiodj@redhat.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