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 16:03:23 -0500 [thread overview]
Message-ID: <cc1649d10802071303i7517c3d1id683a6b1edf227bc@mail.gmail.com> (raw)
In-Reply-To: <cc1649d10802071257r1d65d622sffa0e9a21883d9b@mail.gmail.com>
Just to make it clear this is the versions.
[root@tor bluez-libs-tests]# gcc --version
gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-27)
[root@tor bluez-libs-tests]# uname -a
Linux torv 2.6.21-6.fc7xen #1 SMP Mon Nov 19 07:14:27 EST 2007 i686
i686 i386 GNU/Linux
[root@tor bluez-libs-tests]# ldd ./target/bluez-tests
linux-gate.so.1 => (0x00762000)
libbluetooth.so.2 => /usr/lib/libbluetooth.so.2 (0x00233000)
libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0x002b1000)
[root@tor bluez-libs-tests]# file /usr/lib/libbluetooth.so.2
/usr/lib/libbluetooth.so.2: symbolic link to `libbluetooth.so.2.9.4'
[root@tor bluez-libs-tests]# file /usr/lib/libbluetooth.so.2.9.4
/usr/lib/libbluetooth.so.2.9.4: ELF 32-bit LSB shared object, Intel
80386, version 1 (SYSV), not stripped
--
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
prev parent reply other threads:[~2008-02-07 21:03 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
2008-02-07 21:03 ` Vlad Skarzhevskyy [this message]
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=cc1649d10802071303i7517c3d1id683a6b1edf227bc@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