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 23:29:13 +0200 [thread overview]
Message-ID: <1129498153.24835.34.camel@blade> (raw)
In-Reply-To: <20051016211330.GA32013@localhost.localdomain>
Hi Johan,
> > So how do I create a backtrace with Python for you?
>
> I was thinking of the several lines of "traceback" information that
> python usually prints when the code does something bad. If the program
> is segfaulting without producing any other output I don't really have
> any expecrience in debugging that kind of problems. In the case that we
> have found a bug in the python D-BUS bindings debugging could be even
> harder.
I tested it on two machines running Ubuntu and both are crashing. One
was amd64 and one i386 based. So basically I think that the D-Bus is at
fault here. And there is no debugging output from Python. The only thing
I saw is an segmentation fault.
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
prev parent reply other threads:[~2005-10-16 21:29 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
2005-10-16 21:13 ` Johan Hedberg
2005-10-16 21:29 ` Marcel Holtmann [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=1129498153.24835.34.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 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.