From: 이주영 <tkakel@naver.com>
To: "Marcel Holtmann" <marcel@holtmann.org>,
bluez-devel@lists.sourceforge.net
Subject: RE: Re: [Bluez-devel] I've found a bug in sdp_cstate_get() function.
Date: Thu, 20 Mar 2008 13:01:03 +0900 [thread overview]
Message-ID: <1f1e24ea31c496efd62db585de7b01cf@i61823> (raw)
In-Reply-To: <A6B7F17C-B7E5-4A45-8208-D9C1FBC68C96@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Hi,
The version is latest bluez-utils-3.28.
Thanks.
Regards
jooyoung.
-----Original Message-----
From: "Marcel Holtmann"<marcel@holtmann.org>
To: "이주영"<tkakel@naver.com>; "BlueZ development"<bluez-devel@lists.sourceforge.net>
Cc:
Sent: 08-03-20(목) 01:47:11
Subject: Re: [Bluez-devel] I've found a bug in sdp_cstate_get() function.
Hi,
> I've found a bug in sdp_cstate_get() function.
> (bluez-utils/dist/sdpd/request.c)
> -> memcpy(cstate, (sdp_cont_state_t *)pdata,
> sizeof(sdp_cont_state_t));
> When running this code, "hcid daemon crash" occurred.(memory
> alignment error)
>
> I think there's a bug with (sdp_cont_state_t *)pdata in
> sdp_cstate_get() function.
> I fixed this code.
> -> memcpy(cstate, pdata, sizeof(sdp_cont_state_t));
> Now, hcid daemon doesn't die.
>
which version? This should have been fixed by now. Either in the
latest bluez-utils-3.28 or the CVS.
Regards
Marcel
tkakel님의 블로그
안녕하세요.
[-- Attachment #2: Type: text/html, Size: 4131 bytes --]
next prev parent reply other threads:[~2008-03-20 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 16:03 [Bluez-devel] I've found a bug in sdp_cstate_get() function 이주영
2008-03-19 16:47 ` Marcel Holtmann
2008-03-20 4:01 ` 이주영 [this message]
2008-03-20 12:43 ` Marcel Holtmann
2008-03-20 11:22 ` [Bluez-devel] RFCOMM sockets Fabrizio Guglielmino
2008-03-20 12:45 ` 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=1f1e24ea31c496efd62db585de7b01cf@i61823 \
--to=tkakel@naver.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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