From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24217 invoked by alias); 8 Apr 2003 06:05:36 -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 24209 invoked from network); 8 Apr 2003 06:05:35 -0000 Received: from unknown (HELO sccrmhc02.attbi.com) (204.127.202.62) by sources.redhat.com with SMTP; 8 Apr 2003 06:05:35 -0000 Received: from kegel.com (c-24-126-73-164.we.client2.attbi.com[24.126.73.164]) by sccrmhc02.attbi.com (sccrmhc02) with SMTP id <2003040806053500200s7ithe>; Tue, 8 Apr 2003 06:05:35 +0000 Message-ID: <3E926917.1050900@kegel.com> Date: Tue, 08 Apr 2003 06:05:00 -0000 From: Dan Kegel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313 X-Accept-Language: de-de, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: multithreaded gdbserver again. Should I use gdb5.3, or a snapshot? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00066.txt.bz2 Hi all, I had the multithreaded gdbserver from gdb-5.3 working, but never tried really debugging anything with it. I recently brought it back up, and tried it out a bit. I ran into the usual set of newbie problems, namely: * I didn't have solib-absolute-prefix set properly; this was made clear with the commands break main cont info shared which showed the wrong path. I gave the command set solib-absolute-prefix /opt/cegl-1.5/hardhat/devkit/sh/sh4_le/target and that helped gdb find the shared libraries * The libthread_db.so on the target was stripped, which seems to have caused SIG32 messages. I made sure both gdb and gdbserver had the same unstripped libthread_db.so. I think that got rid of the SIG32's, but... Oddly, gdb doesn't seem to automatically load the shared libraries, even though auto-solib-add is on. I have to give the command shared after hitting the breakpoint at main for the libraries to load, else I get that SIG32 message. Maybe I don't understand how shared libraries get loaded into gdb. I didn't think I should have to give the 'shared' command normally. Any idea what's up there? And even then, I seem to get the SIGTRAP message referred to in http://sources.redhat.com/ml/gdb/2003-03/msg00227.html when I step a bit after hitting a breakpoint in a thread. I tried applying the PREPARE_TO_PROCEED patch Daniel mentioned in http://sources.redhat.com/ml/gdb/2003-03/msg00228.html, and the original patch http://sources.redhat.com/ml/gdb-patches/2002-08/msg01056.html but neither of them seemed to apply cleanly against gdb-5.3. Each had at least one reject. I fixed up the rejects, but the resulting debugger didn't work too well. I'm sure my difficulties are because I'm sleepy, but perhaps it's worth asking: should I stick with gdb5.3, or is a more recent snapshot a better bet? I'm running gdb on x86 linux, and I'm running gdbserver on ppc405, ppc750, and sh4 linux. Thanks, Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045