From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Python/Gtk2 test application for the new D-BUS interface
Date: Sun, 16 Oct 2005 21:24:15 +0200 [thread overview]
Message-ID: <1129490655.24835.22.camel@blade> (raw)
In-Reply-To: <20051016165415.GA31000@localhost.localdomain>
Hi Johan,
> > it crashes with the name resolve on AMD64, but it is a great starting
> > point.
>
> There are some small changes to how name resolving is done in the latest
> version (0.2) available here:
> http://www.iki.fi/~jhedberg/bluez-python/
>
> If you still get the crash, could you perhaps send a backtrace of it? (I
> don't have a 64bit machine to reproduce it on).
it is still crashing. It also happens with the start of periodic inquiry
and both are producing a segmentation fault. If I start the program and
then call 'hcitool scan' the name resolving seems to work flawless.
So how do I create a backtrace with Python for you?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-16 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 21:05 [Bluez-devel] Python/Gtk2 test application for the new D-BUS interface Johan Hedberg
2005-10-16 13:29 ` Marcel Holtmann
2005-10-16 16:54 ` Johan Hedberg
2005-10-16 19:24 ` Marcel Holtmann [this message]
2005-10-16 21:13 ` Johan Hedberg
2005-10-16 21:29 ` 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=1129490655.24835.22.camel@blade \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox