On Wed, 2018-12-05 at 21:33 +0100, Andreas Schneider wrote:
> Hi,
>
> after updating to the newest version from git, Denemo crashes with a
> segmentation fault on startup (after having said No to the question
> whether to re-use existing commands, shortcuts, etc.),
That is the bit that was causi
On Wed, 2018-12-05 at 21:33 +0100, Andreas Schneider wrote:
> Hi,
>
> after updating to the newest version from git, Denemo crashes with a
> segmentation fault on startup (after having said No to the question
> whether to re-use existing commands, shortcuts, etc.), see the
> traceback
> below. Do
Hi,
after updating to the newest version from git, Denemo crashes with a
segmentation fault on startup (after having said No to the question
whether to re-use existing commands, shortcuts, etc.), see the traceback
below. Do you have an idea what might cause that? My OS is Debian
Stretch (9.6).
An
On Thu, 2017-02-09 at 08:50 +0100, Andreas Schneider wrote:
> Am 08.02.2017 um 10:09 schrieb Richard Shann:
> > On Tue, 2017-02-07 at 23:40 +0100, Andreas Schneider wrote:
> >>> is that a parameter to the configure script? That might well turn
[...]
> >
> > But first, check that voices can have ly
Am 08.02.2017 um 10:09 schrieb Richard Shann:
> On Tue, 2017-02-07 at 23:40 +0100, Andreas Schneider wrote:
>>> is that a parameter to the configure script? That might well turn
>> off
>>> the optimizer too.
>>
>> Yes, I meant an additional parameter to the configure script
>
> So it probably turn
On Tue, 2017-02-07 at 23:40 +0100, Andreas Schneider wrote:
> > is that a parameter to the configure script? That might well turn
> off
> > the optimizer too.
>
> Yes, I meant an additional parameter to the configure script
So it probably turned off the optimizer, which then perturbed the code
ge
On Tue, 2017-02-07 at 23:42 +0100, Andreas Schneider wrote:
> >> Do you mean Staffs/Voices > Voices > Add Voice?
> >
> > Does it always do this? That is if you start with an empty score?
>
> No, Denemo does not crash when applying Add Voice to an empty score.
OK, if you then add a verse to the *
Am 07.02.2017 um 23:10 schrieb Richard Shann:
> On Tue, 2017-02-07 at 21:30 +0100, Andreas Schneider wrote:
>>> Could you make the following check:
>>>
>>> start the version of the program that crashes when trying to delete
>> the
>>> last verse. Create a voice to a staff and add a verse to it. Typ
Am 07.02.2017 um 23:11 schrieb Richard Shann:
> On Tue, 2017-02-07 at 21:34 +0100, Andreas Schneider wrote:
>> The difference is that I compiled with the additional flag
>> --enable-debug
>
> is that a parameter to the configure script? That might well turn off
> the optimizer too.
Yes, I meant
On Tue, 2017-02-07 at 21:34 +0100, Andreas Schneider wrote:
> The difference is that I compiled with the additional flag
> --enable-debug
is that a parameter to the configure script? That might well turn off
the optimizer too.
Richard
___
Denemo-de
On Tue, 2017-02-07 at 21:30 +0100, Andreas Schneider wrote:
> > Could you make the following check:
> >
> > start the version of the program that crashes when trying to delete
> the
> > last verse. Create a voice to a staff and add a verse to it. Typeset
> the
> > score and see if the verse that i
Am 07.02.2017 um 10:33 schrieb Richard Shann:
> [...]
>
> I guess you have to have the flag set for debug symbols for the
> breakpoint to get set (IIRC the flag is -B for gcc).
>
> ... and reading a later email, you turned on debug symbols and the
> program didn't crash. This *really* shouldn't ha
Am 07.02.2017 um 11:19 schrieb Richard Shann:
> On Sun, 2017-02-05 at 22:02 +0100, Andreas Schneider wrote:
>> Thread 1 "denemo" received signal SIGINT, Interrupt.
>> 0x71fb754d in poll () at ../sysdeps/unix/syscall-template.S:84
>> (gdb) b select.c:1176
>> Make breakpoint pending on future
On Mon, 2017-02-06 at 21:28 +0100, Andreas Schneider wrote:
> > make clean && make 2>&1 | tee make.log
> >
> > to be sure that there are no warnings being ignored.
>
> You find the output of make attached to this mail.
This has flagged up some interesting things to fix, but nothing
dangero
On Sun, 2017-02-05 at 22:02 +0100, Andreas Schneider wrote:
> Thread 1 "denemo" received signal SIGINT, Interrupt.
> 0x71fb754d in poll () at ../sysdeps/unix/syscall-template.S:84
> (gdb) b select.c:1176
> Make breakpoint pending on future shared library load? (y or [n])
So the other crash
On Sun, 2017-02-05 at 22:08 +0100, Andreas Schneider wrote:
> Am 03.02.2017 um 18:26 schrieb Richard Shann:
> > On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
> >>> Also, if you delete the lyrics from the score I expect the problem
> >> may
> >>> go - it was the snapshotting of the lyr
On Mon, 2017-02-06 at 08:50 +0100, Andreas Schneider wrote:
> I have now seen that the version with debug informations does not
> crash.
> So it might have something to do with the optimisation?
Well optimization is done independently of creating and storing debug
information. To test without opti
Am 06.02.2017 um 08:45 schrieb Andreas Schneider:
> Am 05.02.2017 um 22:02 schrieb Andreas Schneider:
>> Am 03.02.2017 um 17:47 schrieb Richard Shann:
>>> On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
Am 01.02.2017 um 22:48 schrieb Richard Shann:
> yes, but it could be a bug
Am 05.02.2017 um 22:02 schrieb Andreas Schneider:
> Am 03.02.2017 um 17:47 schrieb Richard Shann:
>> On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
>>> Am 01.02.2017 um 22:48 schrieb Richard Shann:
yes, but it could be a bug in Denemo that happens not to be
>>> triggered.
Ca
Am 03.02.2017 um 18:26 schrieb Richard Shann:
> On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
>>> Also, if you delete the lyrics from the score I expect the problem
>> may
>>> go - it was the snapshotting of the lyrics that had serious bugs.
>>
>> When deleting the last lyrics verse,
Am 03.02.2017 um 17:47 schrieb Richard Shann:
> On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
>> Am 01.02.2017 um 22:48 schrieb Richard Shann:
>>> yes, but it could be a bug in Denemo that happens not to be
>> triggered.
>>> Can you try executing
>>> (d-IncreaseGuard) in the Scheme w
On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
> > Also, if you delete the lyrics from the score I expect the problem
> may
> > go - it was the snapshotting of the lyrics that had serious bugs.
>
> When deleting the last lyrics verse, Denemo crashes, even after
> executing (d-Increase
On Thu, 2017-02-02 at 23:33 +0100, Andreas Schneider wrote:
> Am 01.02.2017 um 22:48 schrieb Richard Shann:
> > yes, but it could be a bug in Denemo that happens not to be
> triggered.
> > Can you try executing
> > (d-IncreaseGuard) in the Scheme window or CLI and then seeing if it
> > crashes? d-
Am 01.02.2017 um 22:48 schrieb Richard Shann:
> yes, but it could be a bug in Denemo that happens not to be triggered.
> Can you try executing
> (d-IncreaseGuard) in the Scheme window or CLI and then seeing if it
> crashes? d- IncreaseGaurd will turn off the undo, and this will indicate
> that the
On Wed, 2017-02-01 at 22:35 +0100, Andreas Schneider wrote:
> Am 01.02.2017 um 22:01 schrieb Andreas Schneider:
> > Am 01.02.2017 um 21:40 schrieb Richard Shann:
> >> On Wed, 2017-02-01 at 21:41 +0100, Andreas Schneider wrote:
> >>> I reproducibly encounter a crash with Denemo when in the attached
Thank you!
I nearly didn't find this, as it depended on some random value whether
it would crash or not. It turned out it was triggered off by the "&"
character in the label one of of a commands.
I've fixed the bug, any characters are now ok in labels.
in git now.
Richard
On Mon, 2015-09-21 at 1
Here is the back trace:
Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: Datei oder Verzeichnis nicht gefunden.
(gdb) where
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
#1 0x7591c888 in gtk_text_buffer_
On Sun, 2015-09-20 at 18:57 +0200, Andreas Schneider wrote:
> I can reproduce a crash the following way:
> * Open the command centre.
> * Search for "Second".
> * Repeat the search several times. After the item "Open Repeat Section"
> (i.e. when searching again while that item is active) the progra
I can reproduce a crash the following way:
* Open the command centre.
* Search for "Second".
* Repeat the search several times. After the item "Open Repeat Section"
(i.e. when searching again while that item is active) the program crashes.
Andreas
___
D
On Wed, 2015-05-27 at 20:45 +0200, Andreas Schneider wrote:
> Am 26.05.2015 um 09:15 schrieb Richard Shann:
> > It would seem that this crash happens when clicking on a menu item
> > (I say this because I can see
> >
> > gtk_menu_shell_activate_item ()
> >
> > in the back trace) before Denemo's
On Wed, 2015-05-27 at 20:45 +0200, Andreas Schneider wrote:
> Am 26.05.2015 um 09:15 schrieb Richard Shann:
> > It would seem that this crash happens when clicking on a menu item
> > (I say this because I can see
> >
> > gtk_menu_shell_activate_item ()
> >
> > in the back trace) before Denemo's
Am 26.05.2015 um 09:15 schrieb Richard Shann:
> It would seem that this crash happens when clicking on a menu item
> (I say this because I can see
>
> gtk_menu_shell_activate_item ()
>
> in the back trace) before Denemo's close routine gets called.
>
> If I'm right it would be very surprising i
It would seem that this crash happens when clicking on a menu item
(I say this because I can see
gtk_menu_shell_activate_item ()
in the back trace) before Denemo's close routine gets called.
If I'm right it would be very surprising if clicking on other menu items
worked as there is nothing spec
Am 25.05.2015 um 19:02 schrieb Richard Shann:
> Is that with Debian Jessie? I have Release 7.8(wheezy) and though it
> will hang in a pthread thing on quitting sometimes I don't ever see a
> segmentation fault.
> Are you able to start it under gdb and get a back trace on the
> segmentation fault?
On Mon, 2015-05-25 at 16:59 +0200, Andreas Schneider wrote:
> Am 25.05.2015 um 12:22 schrieb Richard Shann:
> > Well, of course, it should not have crashed in either case. But this is
> > the point of updates to the thread handling made since 1.2.2 so it will
> > only be interesting if it happens
Am 25.05.2015 um 12:22 schrieb Richard Shann:
> Well, of course, it should not have crashed in either case. But this is
> the point of updates to the thread handling made since 1.2.2 so it will
> only be interesting if it happens in the current 1.2.3 (it will be more
> useful to provide a Debian p
On Mon, 2015-05-25 at 12:08 +0200, Andreas Schneider wrote:
> Am 25.05.2015 um 11:52 schrieb Andreas Schneider:
> > On a Debian Jessie with KDE, Denemo 1.2.2 crashes with "Attempt to
> > unlock mutex that was not locked" even at the first launch (after the
> > question whether to re-use old setting
Am 25.05.2015 um 11:52 schrieb Andreas Schneider:
> On a Debian Jessie with KDE, Denemo 1.2.2 crashes with "Attempt to
> unlock mutex that was not locked" even at the first launch (after the
> question whether to re-use old settings, which I answered no):
Oh, by mistake (or rather some bug in the
On a Debian Jessie with KDE, Denemo 1.2.2 crashes with "Attempt to
unlock mutex that was not locked" even at the first launch (after the
question whether to re-use old settings, which I answered no):
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is
possible.
ALSA lib pcm.c:22
Hi,
Am 03.10.2012 13:52, schrieb Richard Shann:
> Thanks for that. I can see a problem with that code, which I have fixed
> and checked in to git.
> In fact,though it seems that this problem was triggered by the presence
> of an entry for a command that no longer exists. I have deleted that
> entr
On Tue, 2012-10-02 at 14:28 -0600, Josue Abarca wrote:
>
> I can confirm this crash.
>
> The last messages in the terminal:
>
> #-
> (denemo:21030): GLib-GObject-WARNING **: invalid cast from `EvView'
> to
The Evince developers have come up with a fix which I have put in
I have put a fix for the bug I identified yesterday, but I don't think
it is your bug. Are you able to run denemo under gdb and report where it
crashes?
Richard
On Tue, 2012-10-02 at 22:22 +0200, Andreas Schneider wrote:
> Hi,
>
> on my installation, the current git version of Denemo crashes
> rep
On Tue, 2012-10-02 at 14:28 -0600, Josue Abarca wrote:
> On Tue, Oct 02, 2012 at 10:22:39PM +0200, Andreas Schneider wrote:
> > Hi,
> >
> > on my installation, the current git version of Denemo crashes
> > reproducably on doing the following:
> >
> > * in the menu, go to Edit > Customize commands
On Tue, 2012-10-02 at 22:22 +0200, Andreas Schneider wrote:
> Hi,
>
> on my installation, the current git version of Denemo crashes
> reproducably on doing the following:
>
> * in the menu, go to Edit > Customize commands, shortcuts > Manage
> command sets
> * click "Load a standard command set"
On Tue, Oct 02, 2012 at 10:22:39PM +0200, Andreas Schneider wrote:
> Hi,
>
> on my installation, the current git version of Denemo crashes
> reproducably on doing the following:
>
> * in the menu, go to Edit > Customize commands, shortcuts > Manage
> command sets
> * click "Load a standard comman
Hi,
on my installation, the current git version of Denemo crashes
reproducably on doing the following:
* in the menu, go to Edit > Customize commands, shortcuts > Manage
command sets
* click "Load a standard command set"
* select Composer.shortcuts and click ok
* Denemo crashes
I am currently on
A short addition: With rc3, the described procedure does not produce a
crash for me.
Andreas
Am 19.05.2012 22:01, schrieb Andreas Schneider:
Hi,
in Denemo 0.9.4rc4 I can reproduce a crash the following way:
* delete your personal configuration directory .denemo-0.9.4 or rename it
* start Den
Hi,
in Denemo 0.9.4rc4 I can reproduce a crash the following way:
* delete your personal configuration directory .denemo-0.9.4 or rename it
* start Denemo
* in the menu, select edit > Customize commands, shortcuts, ... > Manage
command set
* click load standard command set
* select Composer.sho
I pushed a change that fixes this.
Jeremiah
Sent from my Samsung smartphone on AT&T
Richard Shann wrote:
>hmm, I spoke to soon. I did make clean and then make
>and now keysig change is doing some corruption all right.
>Richard
>
>On Thu, 2011-12-01 at 11:07 -0600, Jeremiah Benham wrote:
>> In
hmm, I spoke to soon. I did make clean and then make
and now keysig change is doing some corruption all right.
Richard
On Thu, 2011-12-01 at 11:07 -0600, Jeremiah Benham wrote:
> In master I am now getting a crash when I:
> place an initial keysig
> place notes
> place a keysig change
>
> bt give
I have just
git checkout master
git pull
./autogen.sh
and the made. Everything seems to be working fine.
(gtk2 of course)
I guess you have some configuration thing messed up?
Richard
On Thu, 2011-12-01 at 11:07 -0600, Jeremiah Benham wrote:
> In master I am now getting a crash when I:
> place an
In master I am now getting a crash when I:
place an initial keysig
place notes
place a keysig change
bt gives me this:
#19 0x0805fef2 in scorearea_configure_event (widget=0x85a1078,
event=0x8587ad8)
at draw.c:77
gui = 0x895b5b8
I can recompile with --enable-debug if you need more.
52 matches
Mail list logo
