From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3154 invoked by alias); 26 Aug 2004 19:38:04 -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 3114 invoked from network); 26 Aug 2004 19:37:56 -0000 Received: from unknown (HELO pegasus.siol.net) (193.189.160.40) by sourceware.org with SMTP; 26 Aug 2004 19:37:56 -0000 Received: from kudu.siol.net ([10.10.10.22]) by pegasus.siol.net (InterMail vK.4.03.05.03 201-232-132-103 license 1cbf71897a39210db31154c99f0b4628) with ESMTP id <20040826193755.FPOO4845.pegasus@kudu.siol.net>; Thu, 26 Aug 2004 21:37:55 +0200 Received: from [192.168.0.77] ([193.77.253.13]) by kudu.siol.net (InterMail vK.4.03.05.03 201-232-132-103 license 1cbf71897a39210db31154c99f0b4628) with ESMTP id <20040826193755.KVDJ16288.kudu@[193.77.253.13]>; Thu, 26 Aug 2004 21:37:55 +0200 Message-ID: <412E3C12.5010502@iskramedical.si> Date: Thu, 26 Aug 2004 19:38:00 -0000 From: Hinko Kocevar User-Agent: Mozilla Thunderbird 0.7 (X11/20040615) MIME-Version: 1.0 To: gdb@sources.redhat.com CC: Daniel Jacobowitz , Kris Warkentin Subject: Re: remote debugging and source files - SOLVED References: <412B4B05.8060705@iskramedical.si> <412B5FE6.8080406@iskramedical.si> <412B6515.2030501@iskramedical.si> <412B6ABC.9060804@qnx.com> <412B7E21.2080500@iskramedical.si> <412B82CB.4000503@qnx.com> <412C9AFC.70608@iskramedical.si> <20040825141558.GA27216@nevyn.them.org> <412CA271.2020302@iskramedical.si> In-Reply-To: <412CA271.2020302@iskramedical.si> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2004-08/txt/msg00395.txt.bz2 Hinko Kocevar wrote: > > This would certainly be the case then, I'll update that board and repost... > As you guys pointed out, it helps having same libs and binaries on both target and host side of debugging enviroment. Thanks for sharing your wisdom. But, now that symbols get loaded automagically on shared library event, other set and enabled breakpoints in debugged program don't stop execution?! I already post another topic about this. Now I'm more confident in what is the reason - its probably libraries itself, since debugging worked just fine (except for the symbol loading) with the old ones. Is there any special case with building libraries to be used process of debugging? -- hinko kocevar iskramedical si Hinko Kocevar, developer Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU "Aì rén" | [Analects XII:22]