From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17448 invoked by alias); 3 Mar 2002 17:03:02 -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 17382 invoked from network); 3 Mar 2002 17:03:01 -0000 Received: from unknown (HELO localhost.redhat.com) (66.31.105.161) by sources.redhat.com with SMTP; 3 Mar 2002 17:03:01 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id E05FC3E68; Sun, 3 Mar 2002 12:01:38 -0500 (EST) Message-ID: <3C8256F2.9000704@cygnus.com> Date: Sun, 03 Mar 2002 09:03:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Mattias Wildeman Cc: gdb@sources.redhat.com Subject: Re: Nonblocking GDB stub References: <3C80203E.49EFDC35@acc.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-03/txt/msg00005.txt.bz2 > Hello! > > I've been using GDB for a while, running it with a ARM based board and a > > serial connection (remote debugging). > > To activate GDB, i'll install a breakpoint on the target and connect GDB > throught that. > Standard behavior. > > Now, what i would like to do is to have GDB interact with the target > without the target being stopped. > Yes, this breaks some of the purpose of the debugger, but i would like > to use GDB to analyze memory and datastructures without freezing the > program. The OS i am running do support task-switching, so i was > thinking about making the stub exception_handler non-blocking (e.g. > remove the while(1==1) statement that makes it accept commands until i > kill it), and instead have a call scheduled for it regularly. > > Has anyone had experience with doing this? Or know of any place were i > could get more information on this? Is it even feasible? > > I looked through Google, but was unable to find anything on this level. > > Thank you for your time! Perhaphs have a look through the tracepoints section of the documentation: http://sources.redhat.com/gdb/onlinedocs/gdb_10.html#SEC68 Another option is to look at modifying GDB so that it doesn't stop all threads - instead only specified threads. This is a little bit more ambitious though. Andrew