All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Joost <bluez@frokaschwei.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] bluez-utils 3.30, uClibc, hcid, plugin handling
Date: Sun, 4 May 2008 22:10:42 +0200	[thread overview]
Message-ID: <200805042210.42828@mail.frokaschwei.de> (raw)

Hello,

I had some trouble using hcid from bluez-utils 3.30 on my openwrt-router.
Openwrt uses uClibc, not glibc.

I discovered the following two problems:

1. In eglib/gmodule.c, function g_module_open, line 29 dlopen is used.
The flags for dlopen come from hcid/plugin.c, function plugin_init, line 94.
The flag-value is 0. According to the manpage of dlopen
(http://www.kernel.org/pub/linux/docs/manpages/man-pages-2.79.tar.bz2),
one of RTLD_LAZY or RTLD_NOW has to be set. uClibc checks this and returns an error.

2. hcid needs to be linked with -rdynamic or --export-dynamic. Some functions
in the hcid-executable are used by the plugins. Without -rdynamic uClibc
doesn't resolve the symbols in the plugins resulting in a NULL pointer
dereference and a SIGSEGV. Again, its documented in the man-page of
dlopen.

Wolfram

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-05-04 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 20:10 Wolfram Joost [this message]
2008-05-09 12:35 ` [Bluez-devel] bluez-utils 3.30, uClibc, hcid, plugin handling Marcel Holtmann

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=200805042210.42828@mail.frokaschwei.de \
    --to=bluez@frokaschwei.de \
    --cc=bluez-devel@lists.sourceforge.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.