LMMS crash

[pizio]

Hi,
I am writing because happen often that LMMS crash without any information. Is here any log file where I can understand what was the matter for crashing?
I am using Debian Testing 9

Thanks

[zonkmachine]

Hi,

Yo!

I am writing because happen often that LMMS crash without any information.

Which version of LMMS are you using?
Did you install it as a binary or compile form source?

Is here any log file where I can understand what was the matter for crashing?
I am using Debian Testing 9
Thanks

When LMMS crash under linux you will often find a core dump, a file named 'core' in wherever you've configured the OS to dump core files.
From the man core page:

By default the core file is called core, and is created in the current working directory

You need a debugger like gdb to study the core file. Typically you would run LMMS in gdb like this:

Code: Select all

gdb ./lmms core

and get a backtrace with the 'bt' command.

[pizio]

Thanks for your answer.

I am using LMMS version 1.1.3 and I have installed directly from apt.
In my working directory there is not any file called "core" that I suppose is created installing the gdb file, don't you?

[zonkmachine]

In my working directory there is not any file called "core" that I suppose is created installing the gdb file, don't you?

No. core is generated by linux. gdb is a debugger that you can use to study the core file.
I thought the default in Debian was to generate a core file but I only use Ubuntu and it's derivatives which may differ on this point so I can't really give you a more specific answer.

See if the answers in this thread is of any help.

[pizio]

As I said there is not any core file, it appears to be generated buy using gdb, but let me testing and then I see.

Thanks

[zonkmachine]

it appears to be generated buy using gdb

No. gdb has nothing to do with the generation of the core file.

See this phrase taken from man core.

The default action of certain signals is to cause a process to terminate and produce a core dump file, a disk file containing an image of the process's memory at the time of termination. This image can be used in a debugger (e.g., gdb(1)) to inspect the state of the program at the time that it terminated.