Bug 207868 - chinese/librime: rime_deployer gets segfault on building chinese/brise on 9.3R
Summary: chinese/librime: rime_deployer gets segfault on building chinese/brise on 9.3R
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: lichray
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-10 04:58 UTC by hiroto.kagotani
Modified: 2018-02-12 14:18 UTC (History)
2 users (show)

See Also:


Attachments
make log of chinese/brise (1.03 KB, text/plain)
2016-03-10 04:58 UTC, hiroto.kagotani
no flags Details
gdb log of rime_deployer (4.35 KB, text/plain)
2016-03-10 04:58 UTC, hiroto.kagotani
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description hiroto.kagotani 2016-03-10 04:58:05 UTC
Created attachment 167948 [details]
make log of chinese/brise

While building chinese/brise on 9.3R (amd64 and i386),
the build process stops for rime_deployer getting segmentation fault,
which is a tool installed by chinese/librime.
Building on 10.2R does not have any problem.


Here is the build log:

# make MAKE_JOBS_UNSAFE=yes
===>  License GPLv3 accepted by the user
===>   zh-brise-0.35 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by zh-brise-0.35 for building
===>  Extracting for zh-brise-0.35
===>  License GPLv3 accepted by the user
===>   zh-brise-0.35 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by zh-brise-0.35 for building
=> SHA256 Checksum OK for rime-brise-brise-0.35_GH0.tar.gz.
===>  Patching for zh-brise-0.35
===>   zh-brise-0.35 depends on executable: rime_deployer - found
===>   zh-brise-0.35 depends on executable: gmake - found
===>  Configuring for zh-brise-0.35
===>  Building for zh-brise-0.35
building rime data.
rime_deployer --build  /usr/ports/chinese/brise/work/brise-brise-0.35/data
Makefile:14: recipe for target 'all' failed
gmake: *** [all] Segmentation fault: 11
*** [do-build] Error code 1

Stop in /usr/ports/chinese/brise.
*** [/usr/ports/chinese/brise/work/.build_done.brise._usr_local] Error code 1

Stop in /usr/ports/chinese/brise.


A core file was dumped:

# ls -l work/brise-brise-0.35
...
-rw-------  1 root  wheel  66650112 Mar 10 13:13 rime_deployer.core


To confirm it is not depending on brise data, I tested with librime data.

# cd /usr/ports/chinese/librime
# make extract
# cd work/lib
# rime_deployer --build work/librime-rime-1.1/data/minimal
Segmentation fault
# ls -l
...
-rw-------  1 root  wheel  124518400 Mar 10 13:26 rime_deployer.core


I tried to use gdb to get where the problem is,
but it is more I can handle.

# cd /usr/ports/chinese/librime
# make clean
# make WITH_DEBUG=yes
# gdb work/librime-rime-1.1/bin/rime_deployer 
(gdb) run --build  /usr/ports/chinese/brise/work/brise-brise-0.35/data
Starting program: /usr/ports/chinese/librime/work/librime-rime-1.1/bin/rime_deployer --build  /usr/ports/chinese/brise/work/brise-brise-0.35/data
(no debugging symbols found)...Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/ports/chinese/librime/work/librime-rime-1.1/lib/librime.so.1]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/local/lib/gcc48/libstdc++.so.6]
(no debugging symbols found)...Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/local/lib/gcc48/libgcc_s.so.1]
(no debugging symbols found)...[New LWP 100132]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 806407400 (LWP 100132/rime_deployer)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 806407400 (LWP 100132/rime_deployer)]
0x00000008034a16ee in free () from /lib/libc.so.7
(gdb) where
#0  0x00000008034a16ee in free () from /lib/libc.so.7
#1  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#2  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#3  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#4  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#5  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#6  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#7  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#8  0x0000000801f0c73f in std::vector<YAML::RegEx, std::allocator<YAML::RegEx> >::~vector () from /usr/local/lib/libyaml-cpp.so.0
#9  0x0000000801f39cd5 in YAML::Utils::WriteTag ()
   from /usr/local/lib/libyaml-cpp.so.0
#10 0x0000000801f3a69c in YAML::Utils::ComputeStringFormat ()
   from /usr/local/lib/libyaml-cpp.so.0
#11 0x0000000801f2653b in YAML::Emitter::Write ()
   from /usr/local/lib/libyaml-cpp.so.0
#12 0x0000000800e7accf in ?? ()
   from /usr/ports/chinese/librime/work/librime-rime-1.1/lib/librime.so.1
#13 0x0000000806466d58 in ?? ()
#14 0x00007fffffffd9b0 in ?? ()
#15 0x00007fffffffd7f0 in ?? ()
#16 0x0000000800e78eec in ?? ()
   from /usr/ports/chinese/librime/work/librime-rime-1.1/lib/librime.so.1
#17 0x00007fffffffd9b0 in ?? ()
#18 0x0000000806466d58 in ?? ()
#19 0x0000000802dbc680 in ?? () from /usr/local/lib/gcc48/libstdc++.so.6
#20 0x0000000800e829c9 in ?? ()
   from /usr/ports/chinese/librime/work/librime-rime-1.1/lib/librime.so.1
#21 0x0000000000000500 in ?? ()
#22 0x0000000802dbc680 in ?? () from /usr/local/lib/gcc48/libstdc++.so.6
#23 0x0000000000005f2e in ?? ()
#24 0x00007fffffffd850 in ?? ()
#25 0x0000000000000002 in ?? ()
#26 0x0000000800e7f32f in ?? ()
   from /usr/ports/chinese/librime/work/librime-rime-1.1/lib/librime.so.1
#27 0x0000000000000500 in ?? ()
#28 0x0000000802dbc680 in ?? () from /usr/local/lib/gcc48/libstdc++.so.6
#29 0x0000000000005f2e in ?? ()
#30 0x0000000806466d48 in ?? ()
#31 0x0000000000000002 in ?? ()
#32 0xfae0da7eb156b0aa in ?? ()
#33 0x00007fffffffd8d0 in ?? ()
#34 0x0000000000000002 in ?? ()
#35 0x00007fffffffd870 in ?? ()
#36 0x0000000800e78fe7 in ?? ()
   from /usr/ports/chinese/librime/work/librime-rime-1.1/lib/librime.so.1
#37 0x0000000000000000 in ?? ()
(gdb)
Comment 1 hiroto.kagotani 2016-03-10 04:58:54 UTC
Created attachment 167949 [details]
gdb log of rime_deployer
Comment 2 Walter Schwarzenfeld 2018-01-17 07:18:03 UTC
Is this still relevant?
Comment 3 Walter Schwarzenfeld 2018-02-12 14:18:23 UTC
9.3 and 10.2 are EOL. Buidls fine on 10.4 and 11.1. So I close, overcome by events.