public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@google.com>
To: "Botond Dénes" <bdenes@scylladb.com>
Cc: gdb@sourceware.org
Subject: Re: Stack unwinding for green threads
Date: Mon, 6 Jul 2020 12:48:47 -0500	[thread overview]
Message-ID: <CAPTJ0XEsXOV=0gYUQrtuyDKjscSQp0gb3b1ZP6dwdTec8W4JeQ@mail.gmail.com> (raw)
In-Reply-To: <e442bf31fb064f476cc829cc71767f995495d071.camel@scylladb.com>

On Fri, Jul 3, 2020 at 4:51 AM Botond Dénes <bdenes@scylladb.com> wrote:
>
> Hi,
>
> I'm working on Scylla [1], an application which is built using the
> seastar framework [2]. This framework provides green threads [3] that
> have their own stacks. These threads are created with `setcontext()`
> and later we switch in/out using `setjmp()`/`longjmp()`.
>
> We have a collection of python scripts [4] to help debug Scylla, among
> these we have a utility command which allows switching in/out of these
> green threads in gdb. This command basically (tries) to emulate
> `setjmp()`/`longjmp()` in python, saving and restoring registers. There
> are several problems with this method. For starters it crashes gdb for
> some time now

It may be worth filing a bug for that at
https://sourceware.org/bugzilla/, crashing GDB sounds like a bug.

Christian

  parent reply	other threads:[~2020-07-06 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03  9:50 Botond Dénes
2020-07-03 10:16 ` Andrew Burgess
2020-07-03 17:36   ` Botond Dénes
2020-07-06 17:48 ` Christian Biesinger [this message]
2020-07-07  6:18   ` Botond Dénes

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='CAPTJ0XEsXOV=0gYUQrtuyDKjscSQp0gb3b1ZP6dwdTec8W4JeQ@mail.gmail.com' \
    --to=cbiesinger@google.com \
    --cc=bdenes@scylladb.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).