Hi Jens,
bt command should only print a stacktrace as text - a need only this for
now. Simply copy/paste this text into your next email :).
P.S. I installed ubuntu studio, compiled muse and fabla from source,
loaded your song file. It works ok. Several times I tried to change
presets in different ways - but there was no crash...
So.. may be your stacktrace will tell something new?
Regards,
Andrew
28.07.2015 03:45, Jens Radloff пишет:
Hi Andrew,
Thank you.
But I do not know how to tell gdb to create a dump file. Is this file
normally automatically created in the directory where gdb is started?
I checked this documentation here for relevant information regarding my
question, but I could not find an answer there:
ftp://ftp.gnu.org/old-gnu/Manuals/gdb/html_chapter/gdb_3.html
ftp://ftp.gnu.org/old-gnu/Manuals/gdb/html_chapter/gdb_14.html
When MusE crashed while gdb was running, I typed in "bt", but nothing
happened. Control+c did not have an effect on gdb, too. Then I killed the
MusE process with "kill -9 <process number of muse2>". Then I still
could not stop gdb from running. Somehow I managed to stop gdb from
running, but I do not have a dump file which contains a dump from the
beginning of when I started MusE.
I can only offer you a copy of the information that I could copy from the
console where gdb ran, see the attached file. This file only contains the
last lines of the debugging process.
So how do I create a dump file with gdb with a dump file created which
records all information from the start of MusE until its crash?
Regards,
Jens
Am Montag, 27. Juli 2015 schrieben Sie:
Hi Jens,
27.07.2015 16:56, Jens Radloff пишет:
Hi Andrew,
I have compiled a debug version of the MusE clone and installed it
into
/opt/muse_2.2.1_patched_debug_installation/
You wrote:
Then, build muse in Debug mode and run in under gdb. When it will
crash again, type 'bt' in gdb console and send here :).
I ran gdb in the directory
/opt/muse_2.2.1_patched_debug_installation/bin
with the following command:
gdb muse2
The result is this here (only the last two lines quoted):
--- Snip Beginning ---
Reading symbols from muse2...done.
(gdb)
--- Snip End ---
, and then the cursor waits for an input. But I do not know what to
enter there. Can you help me?
Ahh, I forgot to write:
just type 'run' and press enter. After that muse will start loading
as usual. Make everything until it crash again - it will be like
muse's arranger hangs. When it will happen, switch to gdb console
and type 'bt'+enter.
P.S. my copy is installing now.
So when the crash occurs in MusE, then I type into the gdb console
"bt", right?
Aha :)
Regards,
Andrew
Regards,
Jens
PS: I have another issue regarding MusE 2.2.1, which also occurs in
the clone in my Ubuntu Studio 14.04.2 installation, but I will
report that later.
Am Montag, 27. Juli 2015 schrieb Andrew Deryabin:
Hi Jens,
27.07.2015 08:31, Jens Radloff пишет:
Hi Andrew,
I'll try to install ubuntu studio and recheck there.
That's a good idea.
I applied your troubleshooting solution. Here is the result:
First I installed the qt5 dev packages.
When I then ran "cmake -i" in the muse2 subdirectory of that
clone, I noticed that the cmake routine had found paths to QT5
programms or libraries, so this was good. I then ran "make" and
"sudo make install" from that directory for a new installation
into /opt/muse_2.2.1. Before that I renamed the existing folder
/opt/muse_2.2.1 to
/opt/muse_2.2.1_old. So now I have a fresh installation of MusE
2.2.1.
But I am sorry to tell you that even in this new MusE
installation, compiled against different lilv programs and
libraries (I saw respective *.o-files in the "clone" directory)
and against qt5, the problem still exists. I loaded that med
file which I had sent to you in my first email regarding this
issue (and which does not make that problem I reported on your
machine), then I clicked the start button, then I tried to
change the presets of that Fabla synth (while I noticed that the
context menu, when right-clicking the Fabla synth name in the
Fabla synth track, is now different to my old MusE installation:
it has more entries), but MusE crashes.
Hmm, that's strange. To be sure, that this build of muse not using
external lilv library, run:
ldd /opt/muse_2.2.1/bin/muse2
and there should not be any lilv, sord, serd, etc libraries in the
output.
Then, build muse in Debug mode and run in under gdb. When it will
crash again, type 'bt' in gdb console and send here :).
While you are dealing with this, I'll install fresh copy of ubuntu
studio for testing...
Regards,
Andrew
I have attached two more dump files about this behaviour:
- "dump_I.txt" contains dump information piped to the console
- "dump_II.txt" contains dump information piped to a text file
Could it be that the cmake-configuration found the lilv libraries
which are installed on my machine as Ubuntu packages, and that
"make" compiled against them? I have the following lilv Ubuntu
packages installed in my system:
- liblilv-0-0
- liblilv-dev
- lilv-utils
- python-lilv
All have version "0.16.0-dfsg-1"
If I mark the package "liblilv-0-0" for complete removal, then
synaptic tells me that, if would continue, the package "ardour"
would be removed, but I do not want this, so I did not remove the
lilv packages before I compiled MusE in that directory where I
downloaded that "master of muse (QT5 port) from github".
Regards,
Jens
Am Montag, 27. Juli 2015 schrieb Andrew Deryabin:
Hi Jens,
Thanks for detailed explanation. I tested muse-2.2.1 on my
system with fabla and your attached med file. No crashes in my
case - tried several times to change presets while playing, in
stop transport state - no crashes.
My system in arch 64-bit. May be the reason of crashes in lilv
library+ friends, I'll try to install ubuntu studio and recheck
there.
Now you can do the following:
clone current master of muse (QT5 port) from github
https://github.com/muse-sequencer/muse :
git clone https://github.com/muse-sequencer/muse.git
to build it you have to install qt5 dev libs:
sudo apt-get install qt5-default qttools5-dev qttools5-dev-tools
This version uses bundled versions of lilv library with all
dependences and they are known to work well.
Remove 2.2.1 version.
build new source as usual and test it.
Waiting for results :).
27.07.2015 05:01, Jens Radloff пишет:
Hi Andrew,
Thanks for your reply.
I applied the following steps to resolve the issue, but the
issue still exists:
=> Currently installed git version in my Ubuntu Studio 14.04.2
installation: 1:1.1.9-1ubuntu0.1.
=> I removed the Ubuntu package of git
=> I downloaded the source code of git in version 2.4.6 and
installed it in /opt/git_2.4.6
=> I expanded the PATH variable with information about my
installation
=> I put the paths to the lib directory of my git installation
in a conf file in /etc/ld.so.conf.d/ and ran "ldcdonfig"
=> I installed the package qt5-default from the Ubuntu
repositories. Due to this, the package qt4-default was removed
according to Synaptic.
=> I recompiled and reinstalled the Fabla synth
=> In MusE I opened the med file which contains a Fabla track
(I sent this med file in my first email regarding this issue
to the developer mailing list)
=> Having pressed the start button in this med file, and when
trying to change the Fabla presets (here: to fabla808), then
MusE crashes.
=> Probem can be reproduced when trying to change to a
different Fabla preset
=> Problem still exists
=> I recompiled MusE 2.2.1. Strange that my system still has
the file /usr/bin/qmake-qt4. There are no *qt5* files in
/usr/bin. As I understand this, the compilation of MusE ran
against /usr/bin/qmake-qt4. In my installation, there is a
symlink from this file to the file /usr/lib/i386-
linux-gnu/qt4/bin/qmake
=> I renamed my MusE installation directory /opt/muse_2.2.1 to
/opt/muse_2.2.1
=> I created a new folder /opt/muse_2.2.1
=> I reinstalled MusE in /opt/muse_2.2.1 with the command "sudo
make install"
=> In MusE I opened the med file which contains a Fabla track
(I sent this med file in my first email regarding this issue
to the developer mailing list)
=> Having pressed the start button in this med file, and when
trying to change the Fabla presets (here: to fabla808), then
MusE crashes.
=> Problem still exists
=> In Muse I created a new med file that contains the same
track information in the left pane as the med file that I
tested before (specified above). Only the notes in the right
pane are different in this new med file. I activated loop mode
and saved this new file.
=> Having pressed the start button in this new med file, and
when trying to change the Fabla presets (here: to fabla808),
then MusE crashes.
=> Problem still exists
Any ideas what to do next?
Regards,
Jens
Am Sonntag, 26. Juli 2015 schrieb Andrew Deryabin:
Hi Jens,
Did you try current git version which uses QT5?
I'll now try to check included song file in 2.2.1 version, but
it's unlikely, that this version will get further updates, as
it's based on QT4. Furthermore, current git uses bundled lv2
support libraries and behaves more predictably.
Regards,
Andrew
26.07.2015 09:35, Jens Radloff пишет:
Hi,
I installed the Fabla LV2 synth in my Ubuntu Studio 14.04.2
installation, i.e. I installed this synth from source. I
downloaded the source files from
https://github.com/harryhaaren/openAV-Fabla
, i.e. the zip file which is offered there via the "Download
ZIP" button.
Due to my installation, Fabla is listed now as a LV2 synth in
MusE.
I created a med file with a Fabla track and connected this
track to a midi drum track which contains some drum notes. I
defined a loop region in this med file and activated loop
mode. Then I saved the med file.
When I start this med file having started MusE and having
loaded this med file into MusE, and if I then change the
preset of the Fabla synth to the preset "fabla808", then MusE
chrashes.
This phenomenon cannot get provocated each time these steps
are applied if the med file is freshly loaded, having
started MusE, but often.
Please find attached to this mail the following files:
1. The appropriate med file.
2. Dump file "dump_I.txt": Contains the beginning of the
dump, the end of the dump has been cut. Dump file created by
piping the dump output to a text file.
3. Dump file "dump_II.txt" Contains the end of the dump,
including the segmenation fault. Created by piping the dump
output to the console.
Regards,
Jens
PS: I just discovered a directory called "Fabla LV2-0" ,
which is a subdirectory of the directory where the attached
med file is located. This is the content of the "Fabla
LV2-0" directory:
drwxrwxr-x 2 test test 4,0K Jul 26 08:40 .
drwxrwxr-x 3 test test 4,0K Jul 26 08:28 ..
lrwxrwxrwx 1 test test 49 Jul 26 08:40 CHH_1.wav ->
/usr/local/lib/lv2/fablaHardElectro.lv2/CHH_1.wav
lrwxrwxrwx 1 test test 52 Jul 26 08:28 Classic-808_Clap.wav
-> /usr/local/lib/lv2/fabla808.lv2/Classic-808_Clap.wav
lrwxrwxrwx 1 test test 53 Jul 26 08:28
Classic-808_Clave.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Clave.wav
lrwxrwxrwx 1 test test 59 Jul 26 08:28
Classic-808_Cymbal-high.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Cymbal-high.wav
lrwxrwxrwx 1 test test 56 Jul 26 08:28
Classic-808_Hi_Conga.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Hi_Conga.wav
lrwxrwxrwx 1 test test 54 Jul 26 08:28
Classic-808_Hi_Tom.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Hi_Tom.wav
lrwxrwxrwx 1 test test 57 Jul 26 08:28
Classic-808_Kick_long.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Kick_long.wav
lrwxrwxrwx 1 test test 58 Jul 26 08:28
Classic-808_Kick_short.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Kick_short.wav
lrwxrwxrwx 1 test test 56 Jul 26 08:28
Classic-808_Lo_Conga.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Lo_Conga.wav
lrwxrwxrwx 1 test test 54 Jul 26 08:28
Classic-808_Lo_Tom.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Lo_Tom.wav
lrwxrwxrwx 1 test test 55 Jul 26 08:28
Classic-808_Maracas.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Maracas.wav
lrwxrwxrwx 1 test test 56 Jul 26 08:28
Classic-808_Md_Conga.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Md_Conga.wav
lrwxrwxrwx 1 test test 54 Jul 26 08:28
Classic-808_Md_Tom.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Md_Tom.wav
lrwxrwxrwx 1 test test 56 Jul 26 08:28
Classic-808_Rim_Shot.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Rim_Shot.wav
lrwxrwxrwx 1 test test 57 Jul 26 08:28
Classic-808_Snare_lo1.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Snare_lo1.wav
lrwxrwxrwx 1 test test 57 Jul 26 08:28
Classic-808_Snare_lo2.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Snare_lo2.wav
lrwxrwxrwx 1 test test 57 Jul 26 08:28
Classic-808_Snare_lo3.wav ->
/usr/local/lib/lv2/fabla808.lv2/Classic-808_Snare_lo3.wav
lrwxrwxrwx 1 test test 53 Jul 26 08:40 FX_Chh_01.wav ->
/usr/local/lib/lv2/fablaHardElectro.lv2/FX_Chh_01.wav
lrwxrwxrwx 1 test test 56 Jul 26 08:40 HardHse_K_02.wav ->
/usr/local/lib/lv2/fablaHardElectro.lv2/HardHse_K_02.wav
lrwxrwxrwx 1 test test 58 Jul 26 08:40 HardHse_K_03_B.wav
->
/usr/local/lib/lv2/fablaHardElectro.lv2/HardHse_K_03_B.wav
lrwxrwxrwx 1 test test 58 Jul 26 08:40 Hard_Hse_OHH_1.wav
->
/usr/local/lib/lv2/fablaHardElectro.lv2/Hard_Hse_OHH_1.wav
lrwxrwxrwx 1 test test 52 Jul 26 08:40 hat_open.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/hat_open.wav
lrwxrwxrwx 1 test test 54 Jul 26 08:40 hat_sizzle.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/hat_sizzle.wav
lrwxrwxrwx 1 test test 47 Jul 26 08:40 hat.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/hat.wav
lrwxrwxrwx 1 test test 48 Jul 26 08:40 kick.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/kick.wav
lrwxrwxrwx 1 test test 48 Jul 26 08:40 ride.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/ride.wav
lrwxrwxrwx 1 test test 55 Jul 26 08:40 snare_clean.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/snare_clean.wav
lrwxrwxrwx 1 test test 59 Jul 26 08:40 snare_rim_clean.wav
->
/usr/local/lib/lv2/fablaSavageDrums.lv2/snare_rim_clean.wav
lrwxrwxrwx 1 test test 49 Jul 26 08:40 snare.wav ->
/usr/local/lib/lv2/fablaSavageDrums.lv2/snare.wav
lrwxrwxrwx 1 test test 49 Jul 26 08:40 xFX_6.wav ->
/usr/local/lib/lv2/fablaHardElectro.lv2/xFX_6.wav
lrwxrwxrwx 1 test test 49 Jul 26 08:40 yFX_3.wav ->
/usr/local/lib/lv2/fablaHardElectro.lv2/yFX_3.wav
lrwxrwxrwx 1 test test 49 Jul 26 08:40 yFX_8.wav ->
/usr/local/lib/lv2/fablaHardElectro.lv2/yFX_8.wav
-------------------------------------------------------------
-- -- -- -----------
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
---------------------------------------------------------------
-- -- -----------
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
-----------------------------------------------------------------
-- -----------
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
-------------------------------------------------------------------
----------- _______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
------------------------------------------------------------------------------
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
------------------------------------------------------------------------------
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
