mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: GDB to debug threaded application
Date: Fri, 6 Apr 2018 17:22:45 -0400	[thread overview]
Message-ID: <20180406212245.GB3094@brightrain.aerifal.cx> (raw)
In-Reply-To: <D68389ED-448F-4BFA-AC56-8D5C7032C8F5@gmail.com>

On Fri, Apr 06, 2018 at 11:00:48PM +0200, Micha Nelissen wrote:
> On 6 Apr 2018, at 19:22, Rich Felker <dalias@libc.org> wrote:
> > 
> >> On Fri, Apr 06, 2018 at 06:33:35PM +0200, Micha Nelissen wrote:
> >> Hi all,
> >> 
> >> I have built a cross-toolchain (x86-64 to arm, gcc 5.4.0) with musl
> >> (1.1.16) using buildroot (2017.02). I let buildroot build a gdb for
> >> the arm platform. It runs, but when I debug my application, gdb
> >> hangs after a thread is started. Can't interrupt it, have to kill
> >> -KILL my application from another ssh session.
> >> 
> >> I noticed that there is a libthread_db.so in the glibc-based
> >> toolchain. Do I need something similar for musl? That
> >> libthread_db.so needs libc.so.6 (glibc) so I guess I can't use it
> >> as-is?
> >> 
> >> Thanks for any pointers!
> > 
> > No, musl does not use libthread_db.so, but presence of a glibc version
> > of this library could break things badly. Make sure it's not being
> > built or present in any location gdb might search. Are you using a
> > remote/cross gdb (with gdbserver on the target) or local gdb?
> 
> A local gdb. In the buildroot environment, no libthread_db is present I think.

Can you reproduce this behavior (the hang) with a trivial test program
that starts a thread, or does it only happen with your real
application?

Rich


      reply	other threads:[~2018-04-06 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 16:33 Micha Nelissen
2018-04-06 17:22 ` Rich Felker
2018-04-06 21:00   ` Micha Nelissen
2018-04-06 21:22     ` Rich Felker [this message]

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=20180406212245.GB3094@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).