From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13410 invoked by alias); 28 May 2012 15:05:59 -0000 Received: (qmail 13395 invoked by uid 22791); 28 May 2012 15:05:58 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from www.meduna.org (HELO meduna.org) (92.240.244.38) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 May 2012 15:05:13 +0000 Received: from dial-95-105-165-4-orange.orange.sk ([95.105.165.4] helo=[192.168.130.22]) by meduna.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1SZ1VE-00077o-4t; Mon, 28 May 2012 17:05:09 +0200 Message-ID: <4FC39416.9000600@meduna.org> Date: Mon, 28 May 2012 15:05:00 -0000 From: Stanislav Meduna User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: openocd-devel@lists.sourceforge.net, ecos-devel@ecos.sourceware.org Subject: Re: [OpenOCD-devel] Thread awareness with eCos problem References: <4FB79716.9030101@meduna.org> <20120519144905.GD1398@home.lan> In-Reply-To: <20120519144905.GD1398@home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: stano@meduna.org X-Authenticator: dovecot_plain X-Spam-Score: -6.9 X-Spam-Score-Int: -68 X-Exim-Version: 4.72 (build at 12-May-2011 18:13:45) X-Date: 2012-05-28 17:05:09 X-Connected-IP: 95.105.165.4:55291 X-Message-Linecount: 38 X-Body-Linecount: 25 X-Message-Size: 1571 X-Body-Size: 979 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2012-05/txt/msg00004.txt.bz2 On 19.05.2012 16:49, Paul Fertser wrote: > Basically, if you can load the elf file in gdb and you can "print" the > needed variable, then OpenOCD has access to it too (because it > basically asks gdb for the offset of a variable it needs). Hm, correct me if I'm wrong: I investigated a bit and I'm afraid that the OpenOCD has an easy access to symbols, but the symbols won't help me to get an offset of a field in a structure. One would need either to also get the debug info into OpenOCD or a way to ask the gdb to evaluate a command, which is not supported and the idea was frowned upon some time ago - see the thread at http://sourceware.org/ml/gdb/2008-10/msg00011.html eCos folks: would it be an idea to add a few extra symbols to the scheduler exporting the neded information for the OpenOCD? I'm probably going to implement it anyway, but it would be nice to get the patches accepted into both eCos and OpenOCD. Regards -- Stano