From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Girish Shilamkar <girish@linsyssoft.com>
Cc: gdb@sources.redhat.com
Subject: Re: Backtrace doesn't terminate.
Date: Fri, 17 Mar 2006 15:50:00 -0000 [thread overview]
Message-ID: <1142608971.7975.84.camel@localhost.localdomain> (raw)
In-Reply-To: <1142607030.5756.10.camel@krypton>
Hi Girish,
You need to submit a testcase and a set of steps that people can use to
replicate your problem . I doubt anyone would be able to help you out
without that.
cheers
Ramana
On Fri, 2006-03-17 at 20:20 +0530, Girish Shilamkar wrote:
> 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.
>
next prev parent reply other threads:[~2006-03-17 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 15:48 Girish Shilamkar
2006-03-17 15:50 ` Ramana Radhakrishnan [this message]
2006-03-17 17:06 ` Daniel Jacobowitz
2006-03-20 23:05 ` Girish Shilamkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1142608971.7975.84.camel@localhost.localdomain \
--to=ramana.radhakrishnan@codito.com \
--cc=gdb@sources.redhat.com \
--cc=girish@linsyssoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox