From: Jim Blandy <jimb@codesourcery.com>
To: "Yaki Tebeka" <tebeka@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Resuming a single suspended thread on Linux
Date: Sun, 07 Jan 2007 14:59:00 -0000 [thread overview]
Message-ID: <m3vejiriff.fsf@codesourcery.com> (raw)
In-Reply-To: <9560bc3b0701061449s6d240616o788d93f472a578b8@mail.gmail.com> (Yaki Tebeka's message of "Sun, 7 Jan 2007 00:49:50 +0200")
"Yaki Tebeka" <tebeka@gmail.com> writes:
> I am implementing a special purpose debugger using gdb.
> When a program is being debugged, I load into it a special library
> that runs a thread (inside the debugged process) that reports data to
> the debugger using a socket communication.
>
> This approach works well on Windows (with another debugger engine),
> but when I try to implement it using gdb on Linux, I realize that
> whenever the debugged application execution is suspended (breakpoint /
> etc), my data reporting thread, that runs inside the debugged process,
> is also suspended.
>
> I tried "thread apply X continue", but it seems to continue the entire
> process (which, as far as I understand, is the right behavior on
> Linux).
>
> Does anyone have an idea for a solution to my problem.
Hi --- have you looked at the documentation for 'set
scheduler-locking'? That might work for you.
next prev parent reply other threads:[~2007-01-07 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 22:49 Yaki Tebeka
2007-01-07 14:59 ` Jim Blandy [this message]
2007-01-07 17:00 ` Yaki Tebeka
2007-01-07 23:30 ` Daniel Jacobowitz
2007-01-15 9:47 ` Yaki Tebeka
2007-01-16 7:20 ` Daniel Jacobowitz
2007-01-18 18:36 ` Jim Blandy
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=m3vejiriff.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=tebeka@gmail.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