From: rien <rien@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: flightgear: abort with free() invalid size
Date: Sun, 13 Sep 2020 00:22:31 +0200 [thread overview]
Message-ID: <20200912222231.RQ8Ut8qk8ldlu1jXoibE1ahK1aTk4Zg2msSyznY4hMM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24873@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3171 bytes --]
New comment by rien on void-packages repository
https://github.com/void-linux/void-packages/issues/24873#issuecomment-691561662
Comment:
Passing any other value (a valid path, en empty string, whatever) now causes a segmentation fault in the same function, but with the following backtrace:
```
#0 0x0000555555f9644a in std::deque<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::_M_destroy_data_aux (this=0x7fffffffe020, __first=<error reading variable: Cannot access memory at address 0x706d742f>, __last=<error reading variable: Cannot access memory at address 0x5>) at /usr/include/c++/9.3/bits/deque.tcc:854
#1 0x00007ffff7b17e9d in std::deque<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::_M_destroy_data (__last=..., __first=..., this=0x7fffffffe020) at /usr/include/c++/9.2/bits/stl_deque.h:2110
#2 std::deque<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::~deque (this=0x7fffffffe020, __in_chrg=<optimized out>) at /usr/include/c++/9.2/bits/stl_deque.h:1069
#3 osgDB::Registry::initDataFilePathList (this=0x555556d97cc0) at /builddir/OpenSceneGraph-OpenSceneGraph-3.4.1/src/osgDB/Registry.cpp:506
#4 0x00007ffff7b18403 in osgDB::Registry::initFilePathLists (this=0x555556d97cc0) at /builddir/OpenSceneGraph-OpenSceneGraph-3.4.1/include/osgDB/Registry:388
#5 osgDB::Registry::Registry (this=0x555556d97cc0) at /builddir/OpenSceneGraph-OpenSceneGraph-3.4.1/src/osgDB/Registry.cpp:262
#6 0x00007ffff7b19cdd in osgDB::Registry::instance (erase=erase@entry=false) at /builddir/OpenSceneGraph-OpenSceneGraph-3.4.1/src/osgDB/Registry.cpp:209
#7 0x00007ffff7a89009 in osgDB::RegisterCompressorProxy::RegisterCompressorProxy (this=0x7ffff7b6b770 <compressor_proxy_NullCompressor>, name=..., compressor=<optimized out>) at /builddir/OpenSceneGraph-OpenSceneGraph-3.4.1/src/osgDB/ObjectWrapper.cpp:754
#8 0x00007ffff7a83c81 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/c++/9.2/ext/new_allocator.h:80
#9 _GLOBAL__sub_I_Compressors.cpp(void) () at /builddir/OpenSceneGraph-OpenSceneGraph-3.4.1/src/osgDB/Compressors.cpp:174
#10 0x00007ffff7fe31ea in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7fffffffe2b8, env=env@entry=0x7fffffffe2c8) at dl-init.c:72
#11 0x00007ffff7fe32e9 in call_init (env=0x7fffffffe2c8, argv=0x7fffffffe2b8, argc=1, l=<optimized out>) at dl-init.c:30
#12 _dl_init (main_map=0x7ffff7ffe130, argc=1, argv=0x7fffffffe2b8, env=0x7fffffffe2c8) at dl-init.c:119
#13 0x00007ffff7fd50ca in _dl_start_user () from /lib/ld-linux-x86-64.so.2
#14 0x0000000000000001 in ?? ()
#15 0x00007fffffffe61f in ?? ()
#16 0x0000000000000000 in ?? ()
```
I'm almost suspecting a fault in the c++ stdlib, but then there would be other programs having this issue.
next prev parent reply other threads:[~2020-09-12 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 21:59 [ISSUE] " rien
2020-09-12 22:11 ` rien
2020-09-12 22:12 ` rien
2020-09-12 22:22 ` rien [this message]
2020-09-12 23:17 ` ericonr
2020-09-13 6:26 ` pullmoll
2020-09-13 6:35 ` pullmoll
2020-09-13 7:06 ` pullmoll
2020-09-13 18:12 ` pullmoll
2020-09-13 19:41 ` rien
2020-09-13 19:41 ` [ISSUE] [CLOSED] " rien
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=20200912222231.RQ8Ut8qk8ldlu1jXoibE1ahK1aTk4Zg2msSyznY4hMM@z \
--to=rien@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).