Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] "single step" atomic instruction sequences as a whole on 	PPC
Date: Wed, 09 May 2007 18:34:00 -0000	[thread overview]
Message-ID: <20070509183319.GA29991@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <1178734875.4754.6.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

Hi Luis,

please check the attached two testcases and run them at least 100x etc.

Unfortunately the threaded one fails for me in some 7% of cases IMO due to
a race at the `infrun.c' line:
	remove_status = remove_breakpoints ();

The whole idea of running all the threads of the program to step over the
atomic sequence is problematic as the other threads may hit the inserted
breakpoint.  While this cases is handled it contains a race.

One way would be to use some temporary:
	if (scheduler_mode == schedlock_off)
	  scheduler_mode = schedlock_step;

But I believe one could use the PPC simulation code instead of the whole
breakpoint/resume way?


Regards,
Jan


On Wed, 09 May 2007 20:21:15 +0200, Luis Machado wrote:
> Daniel,
> 
> > Does Ulrich's observation imply that there is no test case for this
> > neat feature?  I would recommend one in gdb.arch (and maybe a NEWS
> > entry too).
> 
> I could work on providing a test case for this feature to be included on
> the GDB testsuite, as soon as i get familiar with the syntax.
> 
> About the instruction bits problem. Should i just literally assign a
> decimal number to the variable (16 in this case) or is it preferred to
> do a shift based on the hex value?
> 
> Thanks!
> Luis

[-- Attachment #2: atomic-seq.tar.gz --]
[-- Type: application/x-gzip, Size: 2768 bytes --]

  reply	other threads:[~2007-05-09 18:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1177964763.15264.45.camel@localhost>
2007-05-02 14:08 ` uweigand
2007-05-03 14:51   ` Luis Machado
2007-05-06 21:20     ` Ulrich Weigand
2007-05-07 15:14       ` Luis Machado
2007-05-07 18:11         ` Ulrich Weigand
2007-05-07 19:28           ` Luis Machado
2007-05-07 22:47             ` Ulrich Weigand
2007-05-07 23:23               ` Luis Machado
2007-05-08 12:50                 ` Ulrich Weigand
2007-05-09 14:33                 ` Ulrich Weigand
2007-05-09 18:05                   ` Luis Machado
2007-05-09 18:12                     ` Daniel Jacobowitz
2007-05-09 18:21                       ` Luis Machado
2007-05-09 18:34                         ` Jan Kratochvil [this message]
2007-05-09 18:46                           ` Daniel Jacobowitz
2007-05-09 19:10                             ` Ulrich Weigand
2007-05-09 19:14                           ` Luis Machado
2007-05-10 10:57                           ` Emi SUZUKI
2007-05-10 21:31                             ` Ulrich Weigand
2007-05-10 21:36                               ` Daniel Jacobowitz
2007-05-10 22:58                                 ` Ulrich Weigand
2007-05-10 23:25                                   ` Daniel Jacobowitz
2007-05-11  7:34                                   ` Emi SUZUKI
2007-05-11 12:46                                     ` Ulrich Weigand
2007-05-09 19:45                         ` Ulrich Weigand
2007-05-10  0:48                           ` Luis Machado
2007-05-10 20:29                             ` Ulrich Weigand
2007-04-09  2:13 Patch for gdb build on hppa hp-ux Daniel Jacobowitz
2007-04-09 23:25 ` Steve Ellcey
2007-04-10 12:05   ` Daniel Jacobowitz
2007-04-10 19:03     ` Eli Zaretskii
2007-04-10 20:22       ` Daniel Jacobowitz
2007-04-13 14:04         ` Daniel Jacobowitz
2007-04-13 17:07           ` [patch] "single step" atomic instruction sequences as a whole on PPC Luis Machado
2007-04-28 23:34             ` [RFC] " Luis Machado
2007-04-28 23:45               ` Ulrich Weigand
2007-04-29  1:53                 ` Luis Machado

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=20070509183319.GA29991@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.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