Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/28/22 1:19 AM, mark_at_yahoo via Rosegarden-user wrote: That said, I've found it lags behind GCC's compiled C++. I've regularly crashed it (crashing the debugger, never a good sign) trying to step though Qt MOC code, to the point where I've given up trying. Ah. Yeah. I don't usually step through code with it. Not sure I've ever crashed gdb, but it's a pain. I usually get enough info from the backtrace to start logging then find the problem. $ cat /proc/sys/kernel/core_pattern core_%E_%p_%i_%s_%t I saw that in the man page. I need to try it out. That could indeed be quite the lifesaver. I think it also mentions something about overwriting too. Probably need to spend some time experimenting. Thanks. Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/27/22 7:28 PM, Ted Felix wrote: There's one more thing to check if core dumps still aren't being created (/proc/sys/kernel/core_pattern). See the wiki for details: https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source#core_dumps There's something new to learn every day. :) > On 5/27/22 9:57 PM, Ted Felix wrote: > I've had no trouble with them at all. Just do a: > > gdb ./rosegarden ./core > > Then "bt" for a backtrace. Works like a charm every time for me. I > think gdb has improved immensely over the years. Yes, of course (`gdb `). If there's a corefile, that is. ;) Yes, GDB has grown by leaps and bounds, e.g. the Python replacement/addition to its original/native scripting language. That said, I've found it lags behind GCC's compiled C++. I've regularly crashed it (crashing the debugger, never a good sign) trying to step though Qt MOC code, to the point where I've given up trying. If I come across that again (by accident or on purpose) and you're interested I'll send the steps to reproduce. On 5/27/22 10:07 PM, Ted Felix wrote: Ok, I found my notes on getting core dumps working everywhere: /etc/security/limits.conf is the right way to do this. Add these lines: * hard core unlimited * soft core unlimited Reboot required. No, I'd already checked that: $ ulimit -c unlimited Now you should have a core dump on every crash. Unless there is already one present. Then it will not write over it, unfortunately. Let me try to return the favor. A little casual reading for pure enjoyment (more like self-inflicted torture) of `man core.5` led me to change from: $ cat /proc/sys/kernel/core_pattern |/bin/false which was inhibiting corefiles by piping them to a null filter, to: $ cat /proc/sys/kernel/core_pattern core_%E_%p_%i_%s_%t which not only enables corefiles but gives each one an overly-detailed unique name (including executable filename, process ID, and universal time) so new ones do *not* overwrite old/existing ones. On 5/27/22 9:57 PM, Ted Felix wrote: > The most irritating part is if I forget to delete the old one before > I do a new run. It won't write over the old one. Definitely > been burned by that in the past. Maybe try something like the above (could also be simplified) and see if you like it. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
There's one more thing to check if core dumps still aren't being created (/proc/sys/kernel/core_pattern). See the wiki for details: https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source#core_dumps Ted. On 5/27/22 10:07 PM, Ted Felix wrote: On 5/27/22 9:57 PM, Ted Felix wrote: I'll see if I can dig up any hints. They can be a bit difficult to get going at first. Ok, I found my notes on getting core dumps working everywhere: /etc/security/limits.conf is the right way to do this. Add these lines: * hard core unlimited * soft core unlimited Reboot required. Now you should have a core dump on every crash. Unless there is already one present. Then it will not write over it, unfortunately. Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/27/22 9:57 PM, Ted Felix wrote: I'll see if I can dig up any hints. They can be a bit difficult to get going at first. Ok, I found my notes on getting core dumps working everywhere: /etc/security/limits.conf is the right way to do this. Add these lines: * hardcoreunlimited * softcoreunlimited Reboot required. Now you should have a core dump on every crash. Unless there is already one present. Then it will not write over it, unfortunately. Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/27/22 6:18 AM, mark_at_yahoo via Rosegarden-user wrote: Sorry, no. Something in my distro turns them off despite ulimit showing unlimited. I'll see if I can dig up any hints. They can be a bit difficult to get going at first. I haven't used corefiles for many years because they were useless more often than not (corrupted stack traces) and instead rely on recreating and trapping on purpose in GDB. I've had no trouble with them at all. Just do a: gdb ./rosegarden ./core Then "bt" for a backtrace. Works like a charm every time for me. I think gdb has improved immensely over the years. The most irritating part is if I forget to delete the old one before I do a new run. It won't write over the old one. Definitely been burned by that in the past. Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
Hi Ted, Thanks for looking into this :-) On 27/05/2022 04:40, Ted Felix wrote: Ok, I think I've got this fixed now. New fix pushed as [6d0a096c]. Please test latest git. Specifically: - Make sure the velocity ruler allows you to adjust the bars one after another when there are no notes selected in Matrix or Notation. Confirmed. - Make sure we don't crash if you delete a Segment that is being edited in Matrix and/or Notation with the velocity ruler visible. Also confirmed. I tested with both the actual matrix/notation windows open when deleting the segment and 'closed'. Lorenzo. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/27/22 2:36 AM, Ted Felix wrote: Did you get a core dump? Or was there an old one in the way? Sorry, no. Something in my distro turns them off despite ulimit showing unlimited. I haven't used corefiles for many years because they were useless more often than not (corrupted stack traces) and instead rely on recreating and trapping on purpose in GDB. But it's a good idea. I'll try to enable them and if I hit this (or anything else) at random maybe there'll be some useful info to report. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/27/22 4:34 AM, mark_at_yahoo via Rosegarden-user wrote: Update: I did get one crash with the new commit but can't recreate it. Had something to do with changing back and forth between selecting in the grid and in the ruler. I think I also deleted segments before it happened. Maybe it's my own strange Qt 5.9.7 build, but something to look out for. I'm sure there are plenty more hiding in there. I'll see if I can exercise it. Did you get a core dump? Or was there an old one in the way? Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
On 5/26/22 7:40 PM, Ted Felix wrote: Ok, I think I've got this fixed now. New fix pushed as [6d0a096c]. Please test latest git. Specifically: - Make sure the velocity ruler allows you to adjust the bars one after another when there are no notes selected in Matrix or Notation. Thanks, Ted. This works as described, although ironically I was not getting the crashes with [329ab4698] either. That said, my personal opinion is that the UI still isn't quite right, at least in the Matrix Editor. With nothing selected in the ME grid, individual notes can be selected in the velocity ruler and their velocities adjusted. But if one or more notes are selected in the grid, they can be adjusted (proportionally if more than one, a great feature) but selecting notes in the velocity ruler no longer works until all are once again deselected in the grid.. I'd like to see selection/adjusting working symmetrically in both grid and ruler: In either interface select and adjust a note, shift-select to add or subtract from the selection and then adjust the selected notes, click-drag-rectangle select a group of notes (this should be added to the velocity tool in addition to the select tool) and then adjust them, etc. I realize this veers off into Feature Request territory and would certainly be after 2022.06 if at all. Time and energy permitting I might hack on it in the context of FR #504 and submit for consideration but thought it appropriate to mention here. Update: I did get one crash with the new commit but can't recreate it. Had something to do with changing back and forth between selecting in the grid and in the ruler. I think I also deleted segments before it happened. Maybe it's my own strange Qt 5.9.7 build, but something to look out for. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] New Crash Related to Velocity Ruler
Ok, I think I've got this fixed now. New fix pushed as [6d0a096c]. Please test latest git. Specifically: - Make sure the velocity ruler allows you to adjust the bars one after another when there are no notes selected in Matrix or Notation. - Make sure we don't crash if you delete a Segment that is being edited in Matrix and/or Notation with the velocity ruler visible. Thanks. Ted. On 5/24/22 7:03 PM, Ted Felix wrote: Looks like my "fix" for the velocity ruler issue (not being able to adjust velocity bars freely) has introduced a new crash. Try deleting a segment that is open in the matrix with the velocity ruler visible. Boom. I'll keep digging... Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
[Rosegarden-user] New Crash Related to Velocity Ruler
Looks like my "fix" for the velocity ruler issue (not being able to adjust velocity bars freely) has introduced a new crash. Try deleting a segment that is open in the matrix with the velocity ruler visible. Boom. I'll keep digging... Ted. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
