From: Daniel Jacobowitz <drow@false.org>
To: Hans Zuidam <h.zuidam@computer.org>
Cc: gdb@sources.redhat.com
Subject: Re: Thread debugging and scheduling behaviour
Date: Thu, 21 Oct 2004 12:52:00 -0000 [thread overview]
Message-ID: <20041020232548.GA14896@nevyn.them.org> (raw)
In-Reply-To: <4C340065-22ED-11D9-9E9C-00039359816C@wanadoo.nl>
On Thu, Oct 21, 2004 at 01:10:56AM +0200, Hans Zuidam wrote:
> Hi,
>
> When running a simple multi-threaded test outside and inside GDB we
> see different scheduling behaviour. This is on a Linux 2.4.20 system.
>
> Specifically the test uses SCHED_FIFO scheduling and fixed priorities.
> What we see is that when run outside GDB the higher priority threads
> run first until they yield, while running in GDB (just a `run' no
> breakpoints) causes low priority threads to run before high priority
> ones.
>
> Is this "expected" Linux behaviour or does it have something to do
> with the thread handling in GDB? Any pointers are greatly appreciated.
GDB does not have any way to support thread priority.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-10-20 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 5:10 Hans Zuidam
2004-10-21 12:52 ` Daniel Jacobowitz [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=20041020232548.GA14896@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=h.zuidam@computer.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