Re: Resuming a single suspended thread on Linux

["Yaki Tebeka" <tebeka at gmail dot com>]

Hi Jim

Thanks for the suggested solution.

I read the "set scheduler-locking" feature documentation few times
(http://sourceware.org/gdb/current/onlinedocs/gdb_6.html#IDX281) and I
must admit that I am not quite sure that I understand it correctly...

One of it sentences says that the other threads are "completely free
to run when you use commands like `continue', `until', or `finish'".
If I understand this correctly, it will not help in my case.

Please let me know if I didn't understand this mechanism correctly.

Yaki


On 1/7/07, Jim Blandy <jimb@codesourcery.com> wrote:
> "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.


--
Yaki Tebeka