From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: test-mesh-crypto segfaults
Date: Mon, 4 Nov 2019 22:16:58 +0100 [thread overview]
Message-ID: <5f75011d-a157-cab2-72df-0209f7a30f21@message-id.googlemail.com> (raw)
Hi,
test-mesh-crypto segfaults for me.
abuild@strolchi:~/rpmbuild/BUILD/bluez-5.52> gdb unit/test-mesh-crypto
[....]
[8.6.2 Service Data using Node Identity]
ID Resolving Key = 84396c435ac48560b5965385253e210c
84396c435ac48560b5965385253e210c => PASS
Hash Input = 00000000000034ae608fbbc1f2c61201
00000000000034ae608fbbc1f2c61201 => PASS
Hash = 00861765aefcc57b
00861765aefcc57b => PASS
Mesh ID Beacon = 0100861765aefcc57b34ae608fbbc1f2c6
0100861765aefcc57b34ae608fbbc1f2c6 => PASS
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7e874ae in mem2chunk_check () from /lib64/libc.so.6
(gdb) bt
#0 0x00007ffff7e874ae in mem2chunk_check () from /lib64/libc.so.6
#1 0x00007ffff7e8b6af in free_check () from /lib64/libc.so.6
#2 0x0000555555557c98 in l_free (ptr=<optimized out>) at ell/util.c:136
#3 l_queue_clear (queue=0x55555556d010, destroy=0x555555557c60
<l_free>) at ell/queue.c:107
#4 0x0000555555557210 in _sub_D_65535_1.7021 () at ell/cipher.c:319
#5 0x00007ffff7fe2c13 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#6 0x00007ffff7e3f877 in __run_exit_handlers () from /lib64/libc.so.6
#7 0x00007ffff7e3fa2c in exit () from /lib64/libc.so.6
#8 0x00007ffff7e27e12 in __libc_start_main () from /lib64/libc.so.6
#9 0x0000555555557b8a in _start () at ../sysdeps/x86_64/start.S:120
this is reproducible here, I'm disabling this test for now in the
openSUSE package build.
Best regards
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
next reply other threads:[~2019-11-04 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 21:16 Stefan Seyfried [this message]
2019-11-04 22:11 ` test-mesh-crypto segfaults Gix, Brian
2019-11-04 22:26 ` Gix, Brian
2019-11-05 9:53 ` Stefan Seyfried
2019-11-05 15:24 ` Stefan Seyfried
2019-11-05 16:31 ` Gix, Brian
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=5f75011d-a157-cab2-72df-0209f7a30f21@message-id.googlemail.com \
--to=stefan.seyfried@googlemail.com \
--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).