Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: tromey@redhat.com
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Allowing all threads of all|current process(es) to be  	resumed [new command + docs]
Date: Sun, 31 May 2009 18:38:00 -0000	[thread overview]
Message-ID: <e394668d0905311138n78b49a6dq6bf8b43e543e92f3@mail.gmail.com> (raw)
In-Reply-To: <m3ljodw2gw.fsf@fleche.redhat.com>

On Sun, May 31, 2009 at 11:29 AM, Tom Tromey <tromey@redhat.com> wrote:
> Doug> # This isn't implementable today, it's just for illustration.
> Doug> define lstep
> [...]
>
> You can implement this with Python today :-) ...
>
> Doug>   set $save_scheduler_locking [get scheduler-locking]
>
> Here you use gdb.parameter.
>
> Doug>   try
>
> Python's try/catch works with gdb exceptions.

Thanks.  I suspected as much, but it was secondary to my main point so
I didn't invest much time in it.


  reply	other threads:[~2009-05-31 18:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 10:51 Pedro Alves
2009-05-30 13:10 ` Eli Zaretskii
2009-05-30 16:01   ` Pedro Alves
2009-05-30 17:12     ` Eli Zaretskii
2009-06-08 11:59       ` Pedro Alves
2009-06-09  4:01         ` Eli Zaretskii
2009-06-11 11:59           ` Pedro Alves
2009-05-31 16:34 ` Doug Evans
2009-05-31 16:40   ` Doug Evans
2009-05-31 18:31   ` Tom Tromey
2009-05-31 18:38     ` Doug Evans [this message]
2009-05-31 22:06     ` Pedro Alves
2009-06-01 15:55       ` Doug Evans
2009-06-03 14:06         ` Pedro Alves
2009-06-01 14:29 ` Marc Khouzam
2009-06-03 13:49   ` 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=e394668d0905311138n78b49a6dq6bf8b43e543e92f3@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tromey@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