From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2004 invoked by alias); 17 Mar 2006 14:56:07 -0000 Received: (qmail 1996 invoked by uid 22791); 17 Mar 2006 14:56:06 -0000 X-Spam-Check-By: sourceware.org Received: from svr68.ehostpros.com (HELO svr68.ehostpros.com) (67.15.48.48) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Mar 2006 14:56:04 +0000 Received: from [59.95.13.60] (helo=titan.linsyssoft.com) by svr68.ehostpros.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FKGMu-0005qu-RO for gdb@sources.redhat.com; Fri, 17 Mar 2006 06:55:57 -0800 Received: from krypton (krypton [192.168.1.13] (may be forged)) by titan.linsyssoft.com (8.13.1/8.13.1) with ESMTP id k2HEf1AU012181 for ; Fri, 17 Mar 2006 20:11:01 +0530 Subject: Backtrace doesn't terminate. From: Girish Shilamkar To: gdb@sources.redhat.com Content-Type: text/plain Date: Fri, 17 Mar 2006 15:48:00 -0000 Message-Id: <1142607030.5756.10.camel@krypton> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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-03/txt/msg00124.txt.bz2 Hi All, I am using gdb 6.4 on Xscale processor. I found that the backtrace doesn't terminate for multi-threaded application, it keeps on repeating the last frame. This problem was also seen on native gdb. (gdb) bt #0 0x401bf06c in nanosleep () from /opt/timesys/toolchains/armv5l-linux/armv5l-linux- debug/lib/libc.so.6 #1 0x401beeb0 in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:137 #2 0x00008574 in thread_func (not_used=0xbee2fba8) at multithread.c:35 #3 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 #4 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 #5 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 #6 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 #7 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 #8 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 On investigating further I found that registers remained unchanged except sp, for these frames. (gdb) fr 3 #3 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 310 in manager.c (gdb) info regi r0 0x0 0 r1 0xbcbff960 -1128269472 r2 0x0 0 r3 0x1 1 r4 0x174 372 r5 0xbcbffbe0 -1128268832 r6 0x0 0 r7 0x400f0d6c 1074728300 r8 0x80 128 r9 0x400eebc0 1074719680 r10 0x400ee000 1074716672 r11 0x0 0 r12 0x0 0 sp 0xbcbffb40 -1128268992 lr 0x400dc0f0 1074643184 pc 0x400dc0f0 1074643184 fps 0x0 0 cpsr 0x60000010 1610612752 (gdb) fr 4 #4 0x400dc0f0 in pthread_start_thread_event (arg=0xbcbffbe0) at manager.c:310 310 in manager.c (gdb) info regi r0 0x0 0 r1 0xbcbff960 -1128269472 r2 0x0 0 r3 0x1 1 r4 0x174 372 r5 0xbcbffbe0 -1128268832 r6 0x0 0 r7 0x400f0d6c 1074728300 r8 0x80 128 r9 0x400eebc0 1074719680 r10 0x400ee000 1074716672 r11 0x0 0 r12 0x0 0 sp 0xbcbffbd8 -1128268840 lr 0x400dc0f0 1074643184 pc 0x400dc0f0 1074643184 fps 0x0 0 cpsr 0x60000010 1610612752 (gdb) Kindly let me know where things might be going wrong. Thanks & Regards, -Girish.