All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dwi Sasongko Supriyadi <ruckuus@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with pthread_mutex_lock with external toolchain
Date: Wed, 22 Jun 2011 14:00:32 +0700	[thread overview]
Message-ID: <BANLkTi=VZ=q7MTfyf453BAAfEqqAZ41Lpg@mail.gmail.com> (raw)

Hello list,

I am testing pcscd of pcsc-lite and I got segmentation fault, following is
the gdb backtrace:

# gdb /usr/sbin/pcscd
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-unknown-linux-gnueabi"...
(no debugging symbols found)
(gdb) run --foreground --debug --apdu
Starting program: /usr/sbin/pcscd --foreground --debug --apdu
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
debuglog.c:277:DebugLogSetLevel() debug level=debug
debuglog.c:306:DebugLogSetCategory() Debug options: APDU
pcscdaemon.c:550:main() pcsc-lite 1.7.2 daemon ready.
[New LWP 1183]

Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 1183]
0x400624e8 in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb)


Has anyone faced the same issue in the past and came up with solution?

Many thanks in advance



--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110622/ca0f85fc/attachment.html>

             reply	other threads:[~2011-06-22  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22  7:00 Dwi Sasongko Supriyadi [this message]
2011-06-22 14:09 ` [Buildroot] Issue with pthread_mutex_lock with external toolchain Dwi Sasongko Supriyadi
2011-06-22 19:53   ` Daniel Nyström
2011-06-23  4:19     ` Dwi Sasongko Supriyadi
2011-07-03 16:59       ` Dwi Sasongko Supriyadi

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='BANLkTi=VZ=q7MTfyf453BAAfEqqAZ41Lpg@mail.gmail.com' \
    --to=ruckuus@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.