Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Fix stale tp->step_resume_breakpoint
Date: Sun, 28 Nov 2010 04:35:00 -0000	[thread overview]
Message-ID: <20101128043440.GB12051@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20101126044756.GB25724@host0.dyn.jankratochvil.net>

On Fri, 26 Nov 2010 05:48:01 +0100, Jan Kratochvil wrote:
> gdb/
> 2010-11-26  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	Fix step_resume_breakpoint unsaved during an infcall.
> 	* gdbthread.h (struct thread_control_state): Move here field
> 	step_resume_breakpoint ...
> 	(struct thread_info): ... from here.
> 	* infrun.c (save_infcall_control_state): Reset
> 	control.step_resume_breakpoint to NULL.
> 	(restore_infcall_control_state, discard_infcall_control_state): Delete
> 	control.step_resume_breakpoint.
> 	* arm-linux-tdep.c, infrun.c, thread.c: Update all the references to
> 	the moved field.
> 
> gdb/testsuite/
> 2010-11-26  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdb.base/step-resume-infcall.exp: New file.
> 	* gdb.base/step-resume-infcall.c: New file.

Checked in:
	http://sourceware.org/ml/gdb-cvs/2010-11/msg00153.html


Thanks,
Jan


      reply	other threads:[~2010-11-28  4:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24  0:51 [patch 3/3] " Jan Kratochvil
2010-11-24 12:43 ` Pedro Alves
2010-11-26  4:46   ` [patch 1/2] Code cleanup: infcall fields moving Jan Kratochvil
2010-11-26 10:36     ` Pedro Alves
2010-11-28  4:34       ` Jan Kratochvil
2010-11-26  4:48   ` [patch 2/2] Fix stale tp->step_resume_breakpoint Jan Kratochvil
2010-11-28  4:35     ` Jan Kratochvil [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=20101128043440.GB12051@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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