Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gomrioje <gomez.j@ikusi.es>
Cc: "Jesús Gómez Río" <gomez.j@ikusi.com>, gdb@sourceware.org
Subject: Re: Debugging pthread in ARM.
Date: Thu, 17 May 2007 12:42:00 -0000	[thread overview]
Message-ID: <20070517124229.GA10918@caradoc.them.org> (raw)
In-Reply-To: <1179405252.6692.65.camel@DAFPC5206.ikusi.net>

On Thu, May 17, 2007 at 02:34:12PM +0200, gomrioje wrote:
> Thanks all, specially Daniel.
> Changing the library libpthread to the right version, 
> let me to set breakpoints in the threads.
> 
> But still something is not working:
> In a simple application, I get an infinite backtrace in the gdb console,
> when it stops in a breakpoint inside a thread.
> (always as:
> #149 0x400c3f78 in pthread_start_thread ()
> from /app/arm/bitbaketmp/staging/arm-linux/lib/libpthread.so.0

I believe a newer GDB will do something more sensible with this.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-05-17 12:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 12:49 gomrioje
2007-05-15 12:58 ` Daniel Jacobowitz
2007-05-15 17:14   ` gomrioje
2007-05-15 17:21     ` Daniel Jacobowitz
2007-05-16 15:27       ` gomrioje
2007-05-16 15:35         ` Daniel Jacobowitz
2007-05-16 17:33           ` gomrioje
2007-05-16 17:38             ` Daniel Jacobowitz
2007-05-16 17:46               ` gomrioje
2007-05-16 17:52                 ` Daniel Jacobowitz
2007-05-16 18:05                   ` gomrioje
2007-05-16 18:11                     ` Daniel Jacobowitz
2007-05-17  8:11                       ` gomrioje
2007-05-17  9:28                         ` Baurzhan Ismagulov
2007-05-17 12:34                       ` gomrioje
2007-05-17 12:42                         ` Daniel Jacobowitz [this message]
2007-05-15 18:42 ` Williams, Allen

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=20070517124229.GA10918@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=gomez.j@ikusi.com \
    --cc=gomez.j@ikusi.es \
    /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