From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18205 invoked by alias); 16 May 2006 16:10:40 -0000 Received: (qmail 18192 invoked by uid 22791); 16 May 2006 16:10:39 -0000 X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.187) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 May 2006 16:10:32 +0000 Received: by nf-out-0910.google.com with SMTP id g2so7140nfe for ; Tue, 16 May 2006 09:10:30 -0700 (PDT) Received: by 10.49.5.11 with SMTP id h11mr4626728nfi; Tue, 16 May 2006 09:10:29 -0700 (PDT) Received: from localhost ( [82.73.179.23]) by mx.gmail.com with ESMTP id a23sm1059253nfc.2006.05.16.09.10.26; Tue, 16 May 2006 09:10:29 -0700 (PDT) Date: Tue, 16 May 2006 18:18:00 -0000 From: Milrith To: gdb@sourceware.org Subject: Problems with remote debugging on ARM Message-Id: <20060516180820.1dcb8eb4.milrith@gmail.com> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00238.txt.bz2 Hello, I encounter a lot of problems while trying to do remote debugging throuh Ethernet on ARM. I try to debug a C++ multithreaded program from Cygwin using a cross-compilation toolchain I built myself (with gdb 6.4). I know this is a complex configuration but maybe somebody would be able to orientate me a bit... I compile my binaries statically as debugging with shared libraries doesn't work (cf. my previous mail), but I have several other problems. I use a timer which is generating a signal every 10 ms (SIGALRM). As soon as timer_settime is called, there is a lot of network activity, the gdb client seems to be busy (when I step) and debugging is unusable. If i increase the period of this timer (to something like 50 ms) it is OK. Would there be a means to still be able to debug my program with the 10 ms period? I have problems with breakpoints not taken into account, are there known problems with some parts of my configuration (C++ or threads)? Thanks in advance, Milrith