From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15581 invoked by alias); 20 Oct 2004 23:11:00 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15574 invoked from network); 20 Oct 2004 23:10:58 -0000 Received: from unknown (HELO smtp05.wanadoo.nl) (194.134.35.145) by sourceware.org with SMTP; 20 Oct 2004 23:10:58 -0000 Received: from [10.0.1.2] (adsl-dc-3f26c.adsl.wanadoo.nl [83.118.144.108]) by smtp5.wanadoo.nl (Postfix) with ESMTP id CB9E19715; Thu, 21 Oct 2004 01:10:57 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4C340065-22ED-11D9-9E9C-00039359816C@wanadoo.nl> Content-Transfer-Encoding: 7bit Reply-To: Hans Zuidam From: Hans Zuidam Subject: Thread debugging and scheduling behaviour Date: Thu, 21 Oct 2004 05:10:00 -0000 To: gdb@sources.redhat.com X-SW-Source: 2004-10/txt/msg00390.txt.bz2 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. With kind regards, Hans Zuidam -- Hans Zuidam Advies tel. +31 40 2481546 De Koppele 136 mob. +31 6 42345456 5632 LD Eindhoven e-mail: h.zuidam@computer.org The Netherlands