From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 202213] bluez trunk tests fail with GCC 9 (or with -fsanitize=address with GCC 9)
Date: Thu, 10 Jan 2019 20:05:29 +0000 [thread overview]
Message-ID: <bug-202213-62941-YuQVZrmgzM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202213-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202213
--- Comment #4 from Stefan Seyfried (stefan.seyfried@googlemail.com) ---
With gcc9 (finally found a way to use it in OBS :-), it asserts:
abuild@strolchi:~/rpmbuild/BUILD/bluez-5.50> cat unit/test-sdp.log
bluetoothd[3066]: Bluetooth daemon 5.50
len: 7 raw_size: 14 cont_len: 0
**
ERROR:unit/test-sdp.c:258:client_handler: assertion failed: ((size_t) len ==
rsp_pdu->raw_size + rsp_pdu->cont_len)
FAIL unit/test-sdp (exit status: 134)
I added a printf before the assert (and shifted it down one line)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-01-10 20:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 13:45 [Bug 202213] New: bluez trunk tests fail with GCC 9 (or with -fsanitize=address with GCC 9) bugzilla-daemon
2019-01-10 16:05 ` [Bug 202213] " bugzilla-daemon
2019-01-10 18:57 ` bugzilla-daemon
2019-01-10 19:16 ` bugzilla-daemon
2019-01-10 20:05 ` bugzilla-daemon [this message]
2019-01-11 9:49 ` bugzilla-daemon
2019-01-11 12:01 ` bugzilla-daemon
2019-01-11 13:07 ` bugzilla-daemon
2019-01-11 13:09 ` bugzilla-daemon
2019-01-11 13:31 ` bugzilla-daemon
2019-01-11 13:53 ` bugzilla-daemon
2019-01-11 16:36 ` bugzilla-daemon
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=bug-202213-62941-YuQVZrmgzM@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).