From: "Vlad Skarzhevskyy" <skarzhevskyy@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sdp_extract_pdu *** stack smashing detected ***
Date: Thu, 7 Feb 2008 15:57:40 -0500 [thread overview]
Message-ID: <cc1649d10802071257r1d65d622sffa0e9a21883d9b@mail.gmail.com> (raw)
In-Reply-To: <1202410007.15090.255.camel@violet>
In fact I used default Fedora 7 and it has bluez-libs 3.9
(libbluetooth.so.2.5.0)
I did source comparison with current sdp.c from bluez-libs 3.25 and I
was not able to see any changer related to this. So I blindly assumed
this may be a bug.
Once bluez-libs 3.25 installed (libbluetooth.so.2.9.4) the original
test works fine but when I change the number of records to 215 I get
the same error. BUT not every run!!!!
--- start testing SDP convenrsions ---
create SEQ of 215 elements
call sdp_attr_add
call sdp_gen_record_pdu
pdu.data_size 438
call sdp_extract_pdu
pdu scanned 438
OK
--- tests finished ---
--- start testing SDP convenrsions ---
create SEQ of 215 elements
call sdp_attr_add
call sdp_gen_record_pdu
make: *** [run] Segmentation fault
If I have #define TEST_SEQ_SIZE 128 (On bluez-libs 3.25 )
When I run the test if fails every 10-th run.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-07 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 20:15 [Bluez-devel] sdp_extract_pdu *** stack smashing detected *** Vlad Skarzhevskyy
2008-02-05 22:40 ` Marcel Holtmann
2008-02-07 18:25 ` Vlad Skarzhevskyy
2008-02-07 18:32 ` Bastien Nocera
2008-02-07 18:54 ` Marcel Holtmann
2008-02-07 18:46 ` Marcel Holtmann
2008-02-07 20:57 ` Vlad Skarzhevskyy [this message]
2008-02-07 21:03 ` Vlad Skarzhevskyy
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=cc1649d10802071257r1d65d622sffa0e9a21883d9b@mail.gmail.com \
--to=skarzhevskyy@gmail.com \
--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