vmap4extractor Segmentation fault

[ghost]

Description:

vmap4extractor Segmentation fault

Current behaviour:

gdb vmap4extractor
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /mnt/WoW_3.3.5_12340/vmap4extractor...(no debugging symbols found)...done.
(gdb) run
Starting program: /mnt/WoW_3.3.5_12340/vmap4extractor
warning: File "/usr/local/lib64/libstdc++.so.6.0.20-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
To enable execution of this file add
        add-auto-load-safe-path /usr/local/lib64/libstdc++.so.6.0.20-gdb.py
line to your configuration file "/root/.gdbinit".
To completely disable this security protection add
        set auto-load safe-path /
line to your configuration file "/root/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
        info "(gdb)Auto-loading safe path"
Extract V4.00 2012_02. Beginning work ....

Game path: Data/
Found locale 'enGB'
Found locale 'enUS'
Found locale 'deDE'
Found locale 'esES'
Found locale 'frFR'
Found locale 'esMX'
Found locale 'ruRU'

Adding data files from locale directories.
Scanning patch levels from data directory.
Scanning patch levels from locale directories.
Locale: enGB
Locale: enUS
Locale: deDE
Locale: esES
Locale: frFR
Locale: esMX
Locale: ruRU

<Some lines.....>

Extracting World\wmo\transports\WMO_elevators\org_arena_ivory_pillar_transport.wmo
Extracting World\wmo\transports\WMO_elevators\org_arena_lightning_pillar_transport.wmo
Extracting World\wmo\transports\WMO_elevators\org_arena_pillar_transport.wmo
Extracting World\wmo\transports\WMO_elevators\ulduarRaid_gnomeWing_transport_WMO.wmo
Extracting World\wmo\transports\icebreaker\Icebreaker_ship_Transport.wmo
Extracting World\wmo\transports\icebreaker\Transport_Icebreaker_ship.wmo
Extracting World\wmo\transports\icebreaker\Transport_Icebreaker_ship_stationary.wmo

Program received signal SIGSEGV, Segmentation fault.
__memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1630
1630            movntdq %xmm1, -0x10(%rdi)
(gdb) bt
#0  __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1630
#1  0x0000000000407374 in MPQFile::read(void*, unsigned long) ()
#2  0x000000000040ba35 in WMOGroup::open() ()
#3  0x0000000000407bf1 in ExtractSingleWmo(std::string&) ()
#4  0x000000000040837f in ExtractWmo() ()
#5  0x00000000004045b6 in main ()

(First start)

---

<Some lines.....>

Map - IcecrownCitadel
Map - IcecrownCitadel5Man
Map - Transport_AllianceAirshipBG
Map - Transport_HordeAirshipBG
Map - Transport_Orgrimmar_to_Thunderbluff
Map - ArgentTournamentRaid
Map - ArgentTournamentDungeon
Map - QuarryofTears
Map - HallsOfReflection
Map - Transport197347
Map - Transport197348
Map - Transport197349
Map - Transport197350
Map - Transport201834
Map - Stormwind
Map - ChamberofAspectsRed
Processing Map 0
[################################################################]
Processing Map 1
[##############################
Program received signal SIGSEGV, Segmentation fault.
__memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:97
97              movdqu  (%rsi), %xmm0
(gdb) bt
#0  __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:97
#1  0x0000000000407374 in MPQFile::read(void*, unsigned long) ()
#2  0x0000000000404f9f in ADTFile::init(unsigned int, unsigned int, unsigned int) ()
#3  0x0000000000407f68 in ParsMapFiles() ()
#4  0x000000000040477e in main ()

(Second start)

---

Branch(es): 3.3.5

Operating system: CentOS Linux release 7.3.1611 (Core)

[Aokromes]

useless crashlog,. compile on debug mode and run again.

[ghost]

git branch -v

• 3.3.5 36bb4ca Core/Spell: add assert checks on SpellMgr::CheckSpellGroupStackRules

git log | head -n 3
commit 36bb4cabae01c591cf6151bae2f65a1f578ed9f3
Author: ariel- <ariel-@users.noreply.github.com>
Date:   Sun Mar 19 04:11:55 2017 -0300

ok, I recompiled with -DWITH_COREDEBUG=1

first run:

#0  __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1630
#1  0x00000000004073a4 in MPQFile::read (this=this@entry=0x7fffffffd560, dest=dest@entry=0x7fffffffd550, bytes=1408336827, bytes@entry=4) at /mnt/TrinityCore/src/tools/vmap4_extractor/mpq_libmpq.cpp:111
#2  0x000000000040ba65 in WMOGroup::open (this=this@entry=0x7fffffffd630) at /mnt/TrinityCore/src/tools/vmap4_extractor/wmo.cpp:160
#3  0x0000000000407c21 in ExtractSingleWmo (fname=...) at /mnt/TrinityCore/src/tools/vmap4_extractor/vmapexport.cpp:200
#4  0x00000000004083af in ExtractWmo () at /mnt/TrinityCore/src/tools/vmap4_extractor/vmapexport.cpp:130
#5  0x00000000004045e6 in main (argc=<optimized out>, argv=<optimized out>) at /mnt/TrinityCore/src/tools/vmap4_extractor/vmapexport.cpp:491

Thanks for answers!

[ghost]

@weboxsm : Please notice that numbers between 1 and 20000 written with a hashtag ( # ) directly in front of it (without spacing) will link to existing issues if they are written in plain text without using a MarkDown block quote ``` before and after the block of text. It is not a big deal here with the low numbers you used (#0 - #5), but it is useful to know later if you write NPC IDs, Quest IDs or similar high numbers while also using hashtags. Linking to numbers in existing issues will look strange, since there is no real connection between such issues.

[edit] Example of such a link (using this issue) : #19327

Also notice that I have added block quotes ``` before and after some of your lines to show you how they can be used to view the text as a non-proportional font/typeface. If you use the "Edit comment" icon on your own post, you will see what I mean. :-)