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 13:25:26 -0500 [thread overview]
Message-ID: <cc1649d10802071025s38dbe8dbuaeff21f05e45b49f@mail.gmail.com> (raw)
In-Reply-To: <1202251232.15090.147.camel@violet>
Hi Marcel
I create a small test in C bluez-sdp-tests.c
Source code there: http://snapshot.bluecove.org/bluecove-gpl/bluez/test/
If the SDP binary size is 258 bytes still works OK.
But when I make it bigger call to sdp_gen_record_pdu will crash.
===================TEST_SEQ_SIZE 125=========================
--- start testing SDP convenrsions ---
create SEQ of 125 elements
call sdp_attr_add
call sdp_gen_record_pdu
pdu.data_size 258
call sdp_extract_pdu
pdu scanned 258
OK
--- tests finished ---
===================TEST_SEQ_SIZE 126=========================
--- start testing SDP convenrsions ---
create SEQ of 126 elements
call sdp_attr_add
call sdp_gen_record_pdu
*** stack smashing detected ***: target/bluez-tests terminated
make: *** [run] Aborted
Regards,
Vlad
-------------------------------------------------------------------------
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 18:25 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 [this message]
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
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=cc1649d10802071025s38dbe8dbuaeff21f05e45b49f@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