From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26194 invoked by alias); 24 Aug 2004 18:05:42 -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 26168 invoked from network); 24 Aug 2004 18:05:40 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sourceware.org with SMTP; 24 Aug 2004 18:05:40 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id NAA07998 for ; Tue, 24 Aug 2004 13:20:10 -0400 Received: from [10.12.1.181] (dhcpa181 [10.12.1.181]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id OAA04237; Tue, 24 Aug 2004 14:02:26 -0400 Message-ID: <412B82CB.4000503@qnx.com> Date: Tue, 24 Aug 2004 18:05:00 -0000 From: Kris Warkentin User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) MIME-Version: 1.0 To: Hinko Kocevar CC: gdb@sources.redhat.com Subject: Re: remote debugging and source files References: <412B4B05.8060705@iskramedical.si> <412B5FE6.8080406@iskramedical.si> <412B6515.2030501@iskramedical.si> <412B6ABC.9060804@qnx.com> <412B7E21.2080500@iskramedical.si> In-Reply-To: <412B7E21.2080500@iskramedical.si> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00337.txt.bz2 Hmm...according to your info shared, you have the loader here: 0x40001460 0x40011914 No /opt/arm-linux/gcc-3.3.3-glibc-2.3.2/arm-softfloat-linux-gnu/lib/ld-linux.so.2 so the breakpoint doesn't seem entirely unreasonable. Is there any possibility that you have a different ld-linux.so.2 on the host and target? Then gdb would be calculating the breakpoint incorrectly based on the host loader. If you take a look at /usr/include/link.h, you'll find the r_debug structure. The comments in there will help you calculate the breakpoint by hand (look at the r_brk element) and then you can compare it to what gdb is coming up with. cheers, Kris Hinko Kocevar wrote: > Kris Warkentin wrote: > >> auto-solib-add will only work properly if gdb successfully sets the >> solib event breakpoint in the loader. Try 'maint info breakpoints' >> and see if it's being set. You could also try setting >> stop-on-solib-events to see if it's actually stopping. Sometimes you >> have problems if there is a different version of the loader on host >> and target. >> > > It seems that solib events have enabled breakpoint, > > (gdb) maintenance info breakpoints > Num Type Disp Enb Address What > -2 longjmp resume keep n 0x00000000 > -3 shlib events keep y 0x4000b8d8 > > but execution won't stop if I do > set stop-on-solib-events 1 > > > regards, > h >