Re: [Bluez-devel] HCID D-Bus (Seg Fault)

[Claudio Takahasi <cktakahasi@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3476 bytes --]

Sorry,

segmentation fault :)

This problem happens because the pin will contains the long error message 
string instead of a short pin number.


On 9/12/05, Claudio Takahasi <cktakahasi@gmail.com> wrote:
> 
> Hi Marcel,
> 
> I am sending a new patch that contains the following enhancements:
> 1. Support multiple D-Bus versions(0.23, 0.30...) 
> 2. Fixed error handling ServiceDoesNotExist, NoReply, UnknownService, ...
> This condition is causing sig fault due the wrong pin value. Scenario: 
> D-Bus pin helper enabled 
> and an error different than wrong argument triggered.
> 
> 
> Regards,
> Claudio.
> 
> On 9/9/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> > 
> > Hi Sjoerd,
> > 
> > > > having 0.33 is better than 0.23 and this is what Debian unstable 
> > still
> > > > uses. However lets make a list of the distributions:
> > > >
> > > > SuSE Linux 10.0 D-Bus 0.35
> > > > Fedora Core 4 D-Bus 0.33
> > > > Ubuntu Breezy D-Bus 0.36
> > > > Debian unstable D-Bus 0.23
> > > Debian experimental D-Bus 0.50
> > 
> > this is good. 
> > 
> > > > The only bad guy is Debian unstable and I don't care anymore. They 
> > use
> > > > Xorg finally and have GCC 4.0 etc., but they can't move over to the 
> > next
> > > > D-Bus generation. I think that is their problem now and the release 
> > of 
> > > > bluez-utils-0.22 will definitely drop the support for the old D-Bus 
> > 0.23
> > > > version.
> > >
> > > D-bus >= 0.3x has been in debian experimental for quite some time. 
> > There are
> > > various transitions going on in debian unstable currently which makes 
> > it 
> > > inappropriate to do a dbus transition now too.
> > 
> > Last time I looked at it, the complete KDE part was broken and full of
> > wrong dependencies. So breaking D-Bus wouldn't even be notified ;)
> > 
> > > > I like to base everything around the current D-Bus 0.50 release, 
> > because
> > > > the C API should be quite stable now. I will accept small 
> > workarounds to
> > > > make D-Bus 0.3x work, but as soon as the distributions update their
> > > > D-Bus libraries I will drop them. 
> > > >
> > > > This is not a nice thing to do, I know, but a wrong usage of D-Bus 
> > lets
> > > > hcid segfault and this is not what I want.
> > >
> > > As one of debian's dbus maintainers i would advise to indeed base 
> > everything on 
> > > dbus >= 0.50. Hopefully it won't take too long before we can move the 
> > new dbus
> > > from experimental to unstable, so the workarounds for old dbus release 
> > are just
> > > not worth it.
> > 
> > This means I will release bluez-utils-2.21 on the weekend, because of
> > some memory leak fixes and then I will drop D-Bus 0.23 support. So if
> > any patches need to go in before, please send them now.
> > 
> > Regards
> > 
> > Marcel
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> > Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & 
> > QA 
> > Security * Process Improvement & Measurement * 
> > http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Bluez-devel mailing list
> > Bluez-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
> > 
> 
> 
>

[-- Attachment #2: Type: text/html, Size: 4855 bytes --]