From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9048 invoked by alias); 11 Feb 2009 17:55:16 -0000 Received: (qmail 9038 invoked by uid 22791); 11 Feb 2009 17:55:14 -0000 X-SWARE-Spam-Status: No, hits=1.3 required=5.0 tests=BARRACUDA_BRBL,BAYES_20,SARE_FREE_WEBM_RuMail,SPF_PASS X-Spam-Check-By: sourceware.org Received: from f36.mail.ru (HELO f36.mail.ru) (194.67.57.74) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Feb 2009 17:55:06 +0000 Received: from mail by f36.mail.ru with local id 1LXJIb-0008Xw-00 for gdb@sourceware.org; Wed, 11 Feb 2009 20:55:01 +0300 Received: from [89.109.29.142] by win.mail.ru with HTTP; Wed, 11 Feb 2009 20:55:01 +0300 From: Dmitry Smirnov To: gdb@sourceware.org Subject: Problem with -stack-list-frames Mime-Version: 1.0 Date: Wed, 11 Feb 2009 17:55:00 -0000 Reply-To: Dmitry Smirnov Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: 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: 2009-02/txt/msg00093.txt.bz2 Hi, I was using gdb-6.8.50.20080630 for a while in the following configuration: - Eclipse CDT as a front end, - gdb-6.8.50.20080630 as ARM debugger connected to skyeye simulator - skyeye simulator as a remote target (server) It was working fine till I had tried to swicth to another (modern) way in CDT debug configuration (called DSF). With the guys that support this new feature, we found that gdb does not respond correctly to -stack-list-frames command. Here is the output, I got from gdb (plus few more commands): info threads * 1 Thread
tmc_init () at qct\services\tmc\tmc.c:11541 warning: RMT ERROR : failed to get remote thread list. -stack-list-frames bt #0 tmc_init () at qct\services\tmc\tmc.c:11541 #1 0x00c1d4c6 in tmc_task (ignored=) at qct\services\tmc\tmc.c:12350 #2 0x00eee43e in rex_thread_init (entrypoint=0xc1d4a9 ) at qct\services\rexl4\rexl4.c:174 #3 0x00f3e0c8 in __thread_stub () #4 0x00f3e0c8 in __thread_stub () Backtrace stopped: previous frame identical to this frame (corrupt stack?) As you can see, info threads and bt works as expected. Don't you know what could be the reason for such a silence of -stack-list-frames? Could you please tell where can start debugging GDB to catch the root cause? BTW, in case you would find it usefull to read the CDT maillist topic, see http://dev.eclipse.org/mhonarc/lists/cdt- dev/msg14275.html Dmitry