Jump to content
  • 0

Core crash when reaching the 2nd metin stone in Devil Tower.


doxiddos

Question

Hi, this source code is using clang,

 

i've compared the code to other sources nothing's different but this crashes

 

gdb:

Core was generated by `./sv1-ch1-core3'.
Program terminated with signal SIGABRT, Aborted.
#0  thr_kill () at thr_kill.S:3
3       thr_kill.S: No such file or directory.
[Current thread is 1 (LWP 100132)]
(gdb) bt
#0  thr_kill () at thr_kill.S:3
#1  0x212b3dbb in raise (s=6) at /usr/src/lib/libc/gen/raise.c:52
#2  0x212313ef in abort () at /usr/src/lib/libc/stdlib/abort.c:67
#3  0x212a48dc in assert (func=0x42738a "instance",
    file=0x427393 "/root/m2-server-src/source/server/game/../common/singleton.h", line=24, failedexpr=0x440f2e "ms_singleton")
    at /usr/src/lib/libc/gen/assert.c:51
#4  0x00911272 in singleton<quest::CQuestManager>::instance ()
    at /root/m2-server-src/source/server/game/../common/singleton.h:24
#5  0x00be83e7 in quest::pc_get_current_map_index (L=0x2fe50d60)
    at /root/m2-server-src/source/server/game/questlua_pc.cpp:575
#6  0x00f25e37 in luaD_precall (L=0x2fe50d60, func=0x2fecaed4)
    at /root/m2-server-src/source/server/liblua/ldo.c:260
#7  0x00f3f60e in luaV_execute (L=0x2fe50d60)
    at /root/m2-server-src/source/server/liblua/lvm.c:627
#8  0x00f26850 in resume (L=0x2fe50d60, ud=0xffffa0e8)
    at /root/m2-server-src/source/server/liblua/ldo.c:344
#9  0x00f25802 in luaD_rawrunprotected (L=0x2fe50d60, f=0xf26770 <resume>,
    ud=0xffffa0e8) at /root/m2-server-src/source/server/liblua/ldo.c:88
#10 0x00f26627 in lua_resume (L=0x2fe50d60, nargs=0)
    at /root/m2-server-src/source/server/liblua/ldo.c:371
#11 0x00baa271 in quest::CQuestManager::RunState (this=0xffffb1d8, qs=...)
    at /root/m2-server-src/source/server/game/questlua.cpp:785

 

gdb bt full

 

#0  0x212b58b3 in ?? ()
No symbol table info available.
#1  0x212313ef in ?? ()
No symbol table info available.
#2  0x00000006 in ?? ()
No symbol table info available.
#3  0x20f50569 in ?? ()
No symbol table info available.
#4  0x20f73000 in ?? ()
No symbol table info available.
#5  0x212a48dc in ?? ()
No symbol table info available.
#6  0x2fecae80 in ?? ()
No symbol table info available.
#7  0x00911272 in singleton<quest::CQuestManager>::instance ()
    at /root/m2-server-src/source/server/game/../common/singleton.h:24
No locals.
#8  0x00be83e7 in quest::pc_get_current_map_index (L=0x2fe50d60)
    at /root/m2-server-src/source/server/game/questlua_pc.cpp:575
No locals.
#9  0x00f25e37 in luaD_precall (L=0x2fe50d60, func=0x2fecaed4)
    at /root/m2-server-src/source/server/liblua/ldo.c:260
        ci = 0x2ff18e30

 

this is where it points me to

 

    int pc_get_war_map(lua_State* L)
    {
        LPCHARACTER ch = CQuestManager::instance().GetCurrentCharacterPtr();
        lua_pushnumber(L, ch->GetWarMap() ? ch->GetWarMap()->GetMapIndex() : 0);
        return 1;
    }

 

 

Edited by doxiddos
Link to post

4 answers to this question

Recommended Posts

  • 0

The quest its not the issue :D i've used this quest on every source i've had

you can find it on any GF files leaked its the normal one not custom

Link to post
  • 0
On 3/16/2021 at 2:04 PM, LordZiege said:

In output it says quest::pc_get_current_map_index

 

And you post 

 

pc_get_war_map

 

I dont think you got the right line

mb sir :D 

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.