Jump to content
×
×
  • Create New...
  • 0

[PROBLEM]40k database error


.Devil.

Question

Hello metin2dev,

i have an error with revision 40k+ database, if I use it, after shutdown give me the error: "Segmentation fault (core dumped)".

If reboot FreeBSD it work again.. What's the problem?

This happen also with the vanilla's dbcache...

If I use the rev 33k it work perfectly.

 

Syserr:

SYSERR: Apr 12 22:59:34 :: pid_init: 
Start of pid: 989

SYSERR: Apr 12 22:59:34 :: Start: TABLE_POSTFIX not configured use default
Link to comment
Share on other sites

  • Answers 15
  • Created
  • Last Reply

Top Posters For This Question

15 answers to this question

Recommended Posts

  • 0

I see..  and thanks for your answer.

But how to solve?

 

This is my db core:

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...Dwarf Error: wrong version in                                   compilation unit header (is 4, should be 2) [in module /metin2/database/db]

Core was generated by `db'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libstdc++.so.6...Error while reading shared library sy                                  mbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in mo                                  dule /lib/libstdc++.so.6]
Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.6
Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x2833c930 in strtoul_l () from /lib/libc.so.7
[New Thread 28406100 (LWP 100272/db)]
[New Thread 28405e00 (LWP 100271/db)]
[New Thread 28405b00 (LWP 100269/db)]
[New Thread 28405800 (LWP 100268/db)]
[New Thread 28405500 (LWP 100267/db)]
[New Thread 28405200 (LWP 100266/db)]
[New Thread 28404f00 (LWP 100265/db)]
[New Thread 28404c00 (LWP 100264/db)]
[New Thread 28404300 (LWP 100076/db)]
Link to comment
Share on other sites

  • 0

Bump..

 

it's not an error just warning ;)

 

Segmantation bug is fixed and public on metin2dev.org. You should be look at topics.

 

Kind Regards

HaveBeen

Today I searched in all forums but I don't have find the fix.. Where is?
 

# Another problem for this is: if start dbcache from start script it don't work, if i start it manually work.

Anybody?..

Link to comment
Share on other sites

  • 0

I've reinstalled my VM and the problem persist. If I try to start database some time it work and I don't understand why.. The solution is not gcc48.

 

If it helps: I use the 9.2 version of FreeBSD.

Link to comment
Share on other sites

  • 0
  • Moon

well i dont now where does the problem came from but try

1-update your FreeBSD (i recommend 9.2 << sence vanilla game work perfectly on them)

2-get the latest lib32.txz

3-reinstall compatx7

other than that try vanilla game only for testing if it work then your problem is from the game

(read the readme.txt file that come with vanilla core)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


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.