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.
+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.
+
2014-01-17 Doug Evans <dje@google.com>
* common/gdb_vecs.c (delim_string_to_char_ptr_vec_append): New
{
enum errors bp_err = GDB_NO_ERROR;
const char *bp_err_message = NULL;
- struct gdb_exception e;
+ volatile struct gdb_exception e;
if (!should_be_inserted (bl) || (bl->inserted && !bl->needs_update))
return 0;
static void
remote_kill (struct target_ops *ops)
{
- struct gdb_exception ex;
+ volatile struct gdb_exception ex;
/* Catch errors so the user can quit from gdb even when we
aren't on speaking terms with the remote system. */