Return-Path: Message-ID: From: Claudio Takahasi To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] HCID D-Bus (Seg Fault) In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16182_25464806.1126559649302" References: <1126220839.5286.57.camel@blade> <5256d0b050909012577fcb19c@mail.gmail.com> <1126258645.5227.16.camel@blade> <20050909132940.GE17543@spring.luon.net> <1126273252.5227.119.camel@blade> Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 12 Sep 2005 18:14:09 -0300 ------=_Part_16182_25464806.1126559649302 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sorry, segmentation fault :) This problem happens because the pin will contains the long error message= =20 string instead of a short pin number. On 9/12/05, Claudio Takahasi wrote: >=20 > Hi Marcel, >=20 > I am sending a new patch that contains the following enhancements: > 1. Support multiple D-Bus versions(0.23, 0.30...)=20 > 2. Fixed error handling ServiceDoesNotExist, NoReply, UnknownService, ... > This condition is causing sig fault due the wrong pin value. Scenario:=20 > D-Bus pin helper enabled=20 > and an error different than wrong argument triggered. >=20 >=20 > Regards, > Claudio. >=20 > On 9/9/05, Marcel Holtmann wrote: > >=20 > > Hi Sjoerd, > >=20 > > > > having 0.33 is better than 0.23 and this is what Debian unstable=20 > > 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 > >=20 > > this is good.=20 > >=20 > > > > The only bad guy is Debian unstable and I don't care anymore. They= =20 > > use > > > > Xorg finally and have GCC 4.0 etc., but they can't move over to the= =20 > > next > > > > D-Bus generation. I think that is their problem now and the release= =20 > > of=20 > > > > bluez-utils-0.22 will definitely drop the support for the old D-Bus= =20 > > 0.23 > > > > version. > > > > > > D-bus >=3D 0.3x has been in debian experimental for quite some time.= =20 > > There are > > > various transitions going on in debian unstable currently which makes= =20 > > it=20 > > > inappropriate to do a dbus transition now too. > >=20 > > 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 ;) > >=20 > > > > I like to base everything around the current D-Bus 0.50 release,=20 > > because > > > > the C API should be quite stable now. I will accept small=20 > > workarounds to > > > > make D-Bus 0.3x work, but as soon as the distributions update their > > > > D-Bus libraries I will drop them.=20 > > > > > > > > This is not a nice thing to do, I know, but a wrong usage of D-Bus= =20 > > lets > > > > hcid segfault and this is not what I want. > > > > > > As one of debian's dbus maintainers i would advise to indeed base=20 > > everything on=20 > > > dbus >=3D 0.50. Hopefully it won't take too long before we can move t= he=20 > > new dbus > > > from experimental to unstable, so the workarounds for old dbus releas= e=20 > > are just > > > not worth it. > >=20 > > 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. > >=20 > > Regards > >=20 > > Marcel > >=20 > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20 > > Practices > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing &= =20 > > QA=20 > > Security * Process Improvement & Measurement *=20 > > http://www.sqe.com/bsce5sf > > _______________________________________________ > > Bluez-devel mailing list > > Bluez-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bluez-devel > >=20 >=20 >=20 > ------=_Part_16182_25464806.1126559649302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sorry,

segmentation fault :)

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


On 9/12/05, Claudio Takahasi <ck= takahasi@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. S= cenario: D-Bus pin helper enabled
   and an error different than wrong argument triggered.
 

Regards,
Claudio.

On 9/9/05, Marcel Holtmann <marcel@ho= ltmann.org > wrote:
Hi Sjoerd,

> > having 0.33 is better than 0.23 and this is wha= t Debian unstable still
> > uses. However lets make a list of the = distributions:
> >
> >     SuSE Linux= 10.0         D-Bus=20 0.35
> >     Fedora Core 4   &n= bsp;       D-Bus 0.33
> >  = ;   Ubuntu Breezy        =    D-Bus 0.36
> >     Debian unstabl= e         D-Bus 0.23
> &= nbsp;   Debian experimental D-Bus 0.50

this is good.

> > The only bad guy is Debian unstable and I don't care anym= ore. 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 the= ir 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 >=3D 0.3x has be= en in debian experimental for quite some time. There are
> various tr= ansitions 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 depende= ncies. So breaking D-Bus wouldn't even be notified ;)

> > I li= ke to base everything around the current D-Bus=20 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 wr= ong usage of D-Bus lets
> > hcid segfault and this is not what I w= ant.
>
> As one of debian's dbus maintainers i would advise to = indeed base everything on
> dbus >=3D 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 wi= ll release=20 bluez-utils-2.21 on the weekend, because of
some memory leak fixes and t= hen I will drop D-Bus 0.23 support. So if
any patches need to go in befo= re, 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 & P= lan-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/list= info/bluez-devel



------=_Part_16182_25464806.1126559649302-- ------------------------------------------------------- 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