From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6604 invoked by alias); 20 Aug 2010 08:33:21 -0000 Received: (qmail 6593 invoked by uid 22791); 20 Aug 2010 08:33:19 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_05 X-Spam-Check-By: sourceware.org Received: from static.88-198-202-190.clients.your-server.de (HELO kleinhenz.com) (88.198.202.190) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Aug 2010 08:33:02 +0000 Received: from localhost (dslb-092-075-161-131.pools.arcor-ip.net [92.75.161.131]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Simon Richter", Issuer "CA Cert Signing Authority" (verified OK)) by kleinhenz.com (Postfix) with ESMTP id 261AE4638FD for ; Fri, 20 Aug 2010 08:29:51 +0200 (CEST) Date: Fri, 20 Aug 2010 08:33:00 -0000 From: Simon Richter To: gdb@sourceware.org Subject: PT_TEXT_ADDR on ARM Message-ID: <20100820083257.GA3902@richter> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-08/txt/msg00123.txt.bz2 Hi, I'm a bit unsure on how to proceed here: ARM has two different definitions for PT_TEXT_ADDR, "49*4" in 2.4 uClinux and "0x10000" in current Linux, which appears to be used on systems without a MMU as well. The former definition "emulates" the behaviour of the Coldfire port, and I've made a working gdbserver for such a system by simply enabling the #ifdef'd code in linux-low.c, however that will most likely fail on more recent kernels. I'd like to prepare a patch that ideally fixes both 2.4 uClinux and 2.6 uClinux (normal Linux doesn't really need the offsets). Should I a) check the kernel version b) try 0x10000 first, if it returns zero, use the value from 0xc4 c) use 0x10000 only? Simon