From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4760 invoked by alias); 27 Jul 2002 00:12:25 -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 4753 invoked from network); 27 Jul 2002 00:12:24 -0000 Received: from unknown (HELO racerx.ixiacom.com) (64.60.75.69) by sources.redhat.com with SMTP; 27 Jul 2002 00:12:24 -0000 Received: from ixiacom.com (dank.ixiacom.com [192.168.3.117]) by racerx.ixiacom.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PMBM7CYY; Fri, 26 Jul 2002 17:10:21 -0700 Message-ID: <3D41EF27.9070204@ixiacom.com> Date: Fri, 26 Jul 2002 17:12:00 -0000 From: Dan Kegel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020615 Debian/1.0.0-3 MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: gdbserver multithread support broken in 5.2.1? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg00295.txt.bz2 With gdb+dejagnu-weekly-CVS-20020709, remote debugging works fine on ppc405. With gdb-5.2.1 built the same way, it doesn't seem to work, and I get the error message GDB bug: target.c (target_signal_from_host): unrecognized real-time signal from gdbserver. The problem seems to be in gdbserver, as the new gdb works fine with the old gdbserver. When I debug a trivial 9-threaded program: the breakpoint on main works fine, but a breakpoint on the first created thread's main routine fails. Here's the gdb log: (gdb) target remote 10.0.1.1:1234 Remote debugging using 10.0.1.1:1234 0x30013ae8 in ?? () (gdb) break main Breakpoint 1 at 0x10000a00: file atomicity_test.c, line 46. (gdb) cont Continuing. Breakpoint 1, main (argc=1, argv=0x7ffffe84) at atomicity_test.c:46 46 int switches = 0; (gdb) break my_thread_main Breakpoint 2 at 0x10000964: file atomicity_test.c, line 33. (gdb) cont Continuing. And here's the log on the remote system: # gdbserver foo:1234 ./a.out Process ./a.out created; pid = 452 Remote debugging from host 192.168.6.130 nthreads 8, nloops 100000, nrepeats 100 GDB bug: target.c (target_signal_from_host): unrecognized real-time signal There wasn't much time between those two releases, so it shouldn't be too hard to track the problem down. I haven't looked at the diffs yet; I was kind of hoping somebody would know what was up... (In both cases, I had applied a patch to give an initial value for solib-absolute-prefix, but it's hard to imagine that was causing a problem...) Thanks for any suggestions! - Dan