Metin2 How to analyze a core dump (game.core/db.core)

[Ionut Barbescu]

How to analyze a core dump (game.core/db.core)
​

How many times has it happened that the core crashes generating a .core and you don't know the reason? This guide will explain how to read the .core (like the game.core) to understand the cause of the crash.

​

We usually use the GDB (gnu debugger) to achieve this.

We go to the relative path in which the executable and the core dump has been generated and start gdb.

After that, we send some specific instructions.

To view the content, you need to Sign In or Register.

In case it says "dwarf error", you have to install the latest gdb and run it as gdbXXX instead of gdb, for example:

To view the content, you need to Sign In or Register.

The instruction bt full returns the full backtrace, instead of doing just bt.

On updated fbsd versions, the gnutarget may be i386-portbld-freebsd10.1 instead of i386-marcel-freebsd.

Important: the executable must be the original one; recompiled executables will give mismatched results.

To view the content, you need to Sign In or Register.

Credits by MartySama0134

 

[Raikiri]

Thanks, very usefull topic! I was looking for this some time ago.

 

[q963123]

He told me how to check the error in game.core

 

[q963123]

He taught me how to use gbd

 

[GnarMain]

How to analyze a core dump (game.core/db.core)
​

How many times has it happened that the core crashes generating a .core and you don't know the reason? This guide will explain how to read the .core (like the game.core) to understand the cause of the crash.

​

We usually use the GDB (gnu debugger) to achieve this.

We go to the relative path in which the executable and the core dump has been generated and start gdb.

After that, we send some specific instructions.

*** Hidden text: cannot be quoted. ***


In case it says "dwarf error", you have to install the latest gdb and run it as gdbXXX instead of gdb, for example:

*** Hidden text: cannot be quoted. ***


The instruction bt full returns the full backtrace, instead of doing just bt.

On updated fbsd versions, the gnutarget may be i386-portbld-freebsd10.1 instead of i386-marcel-freebsd.

Important: the executable must be the original one; recompiled executables will give mismatched results.

*** Hidden text: cannot be quoted. ***

Credits by MartySama0134

ty

 

[q963123]

GGG

 

[samirmagde1212m]

How to analyze a core dump (game.core/db.core)
​

How many times has it happened that the core crashes generating a .core and you don't know the reason? This guide will explain how to read the .core (like the game.core) to understand the cause of the crash.

​

We usually use the GDB (gnu debugger) to achieve this.

We go to the relative path in which the executable and the core dump has been generated and start gdb.

After that, we send some specific instructions.

*** Hidden text: cannot be quoted. ***


In case it says "dwarf error", you have to install the latest gdb and run it as gdbXXX instead of gdb, for example:

*** Hidden text: cannot be quoted. ***


The instruction bt full returns the full backtrace, instead of doing just bt.

On updated fbsd versions, the gnutarget may be i386-portbld-freebsd10.1 instead of i386-marcel-freebsd.

Important: the executable must be the original one; recompiled executables will give mismatched results.

*** Hidden text: cannot be quoted. ***

Credits by MartySama0134

thx

 

[Saliba]

How to analyze a core dump (game.core/db.core)
​

How many times has it happened that the core crashes generating a .core and you don't know the reason? This guide will explain how to read the .core (like the game.core) to understand the cause of the crash.

​

We usually use the GDB (gnu debugger) to achieve this.

We go to the relative path in which the executable and the core dump has been generated and start gdb.

After that, we send some specific instructions.

*** Hidden text: cannot be quoted. ***


In case it says "dwarf error", you have to install the latest gdb and run it as gdbXXX instead of gdb, for example:

*** Hidden text: cannot be quoted. ***


The instruction bt full returns the full backtrace, instead of doing just bt.

On updated fbsd versions, the gnutarget may be i386-portbld-freebsd10.1 instead of i386-marcel-freebsd.

Important: the executable must be the original one; recompiled executables will give mismatched results.

*** Hidden text: cannot be quoted. ***

Credits by MartySama0134

Thank You