public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Nikita V. Youshchenko" <alexmm@gala.net>
To: gdb@sources.redhat.com
Subject: A question about gcc and threads under Linux 2.4
Date: Tue, 18 Mar 2003 10:46:00 -0000	[thread overview]
Message-ID: <200303181345.10851@zigzag.cs.msu.su> (raw)

Hello.

When debugging threaded programs with gdb, unexpected thread switches often 
happen. E.g. if another gdb step-by-step executes one thread, and another 
thread executes a system call, ofted gdb switches to than thread.

Gdb documentation says that on some targets gdb supports "set 
scheduler-locking" command that can help to avoid this behaviuor. But 
seems that this is not supported under Linux.

Is there any method to make debugging threads smarter under Linux? E.g. a 
kernel patch, another threading library, some patch to gdb, etc? If there 
are none, could someone assist me it implementing one?

Thank you for your help.
Please CC: me, I am not on the list.

             reply	other threads:[~2003-03-18 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 10:46 Nikita V. Youshchenko [this message]
2003-03-18 16:58 ` Daniel Jacobowitz
2003-03-21 18:16   ` Re[2]: " Nikita V . Youshchenko

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=200303181345.10851@zigzag.cs.msu.su \
    --to=alexmm@gala.net \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).