From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19165 invoked by alias); 27 Oct 2003 18:00:43 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 19152 invoked from network); 27 Oct 2003 18:00:42 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 27 Oct 2003 18:00:42 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h9RI0gM24198 for ; Mon, 27 Oct 2003 13:00:42 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h9RI0g623215; Mon, 27 Oct 2003 13:00:42 -0500 Received: from redhat.com (to-dhcp19.toronto.redhat.com [172.16.14.119]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h9RI0f6q027630; Mon, 27 Oct 2003 13:00:41 -0500 Message-ID: <3F9D6B6A.8070302@redhat.com> Date: Mon, 27 Oct 2003 18:00:00 -0000 From: Keith Seitz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901 X-Accept-Language: en-us MIME-Version: 1.0 To: L P CC: insight@sources.redhat.com Subject: Re: Can not interrupt running application References: <20031027093829.33429.qmail@iname.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q4/txt/msg00059.txt.bz2 L P wrote: > Hello. > I reread my mail and decided to add some more details. > I cross-compiled Insight 5.3 on RH9 machine with gcc5.2.2 for PowerPC. > I try to debug my embedded application via the BDM using bdm4gdb package. > When I run the application by plane gdb in console mode, 100% of gdb works and when I press Ctrl-C (while the application is in while(1) > loop) gdp stops saying "Program received signal SIGINT, Interrupt.". > When I try to do the same in Insight, it hangs. I can not press any button (including interrupt) or enter any menu item. Only kill command > helps. > > What can be the cause of the problem? Sounds a lot like another backend problem with the bdm code. To be specific... Gdb has several event loops. Insight adds another. The two really important event loops are the Tk event loop (used by Insight's GUI code) and gdb's target_wait (which waits for an event from the target). When using a serial port or a network connection in one of gdb's standard/supported targets, the target_wait loop will call out to a hook which will keep the UI alive (ui_loop_hook). This is done all over the place. It isn't pretty, but it's the only workable solution right now. (Well, actually that may not be necessarily true anymore, since we can now monitor activity on a socket for windows events in both X and cygwin. Nonetheless, it wasn't always possible, and this is what we have today.) It sounds a lot like the bdm code is waiting forever for an event from the target, and starving the UI event loop. Keith