From: "Botond Dénes" <bdenes@scylladb.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb@sourceware.org
Subject: Re: Stack unwinding for green threads
Date: Tue, 07 Jul 2020 09:18:04 +0300 [thread overview]
Message-ID: <60e880f0df120996da164e379dc0323fd2069cf2.camel@scylladb.com> (raw)
In-Reply-To: <CAPTJ0XEsXOV=0gYUQrtuyDKjscSQp0gb3b1ZP6dwdTec8W4JeQ@mail.gmail.com>
On Mon, 2020-07-06 at 12:48 -0500, Christian Biesinger wrote:
> 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.
We see a lot of crashes of GDB at ScyllaDB. Yes, I should get into the
habit of reporting these.
>
> Christian
prev parent reply other threads:[~2020-07-07 6:18 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
2020-07-07 6:18 ` Botond Dénes [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=60e880f0df120996da164e379dc0323fd2069cf2.camel@scylladb.com \
--to=bdenes@scylladb.com \
--cc=cbiesinger@google.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).