2.56.0-2ubuntu1), and the issue could not be reproduced, even though glib libraries had no debug symbols. However, I also tested this issue in a VM running Ubuntu 18.04 (with libglib2.0-0 ver. Output from that test is attached (mocha_ardour_nocrash_output). Using glib 2.56 w/ debug symbols, the issue did not occur. I then compiled glib 2.56 with debug symbols, as described by Cameron with the `debug !strip` options in the PKGBUILD. Backtrace from gdb is attached (mocha_ardour_backtrace). I reproduced the issue on Arch (as documented in the Ardour bug tracker link) with Ardour 6.0-pre0 (compiled with debug symbols) and glib 2.56 (compiled w/o debug symbols). _commit=66948ae231f75a548c8a2eb7b3a9d64cfd728b8e # glib-2-56Īs someone else with this issue, I thought I might chime in with some testing I've done. Optdepends=('python: gdbus-codegen, glib-genmarshal, glib-mkenums, gtester-report' +++ -14,7 +14,7 makedepends=(gettext gtk-doc shared-mime-info python libelf git util-linux dbus)
Ardour 5.12 Patch#
More specifically, building and installing the following PKGBUILD with and without the following patch are enough to cause the issue: The only changes in the build process should be: If you have any idea how we can debug this build where enabling debugging fixes the issue, please advise lol Building the same package without debugging support causes the issue still. You somehow led me to a solution, so thanks again!Īctually, this is reproducible. In any case, this is not meaningfully reproducible. Now I wonder if the issue was with the packaging. Something about building glib2 on my machine instead of using the distribution package seems to have resolved this. it worked! I know I was using 2.56.0 before because I ran ldd on the binary during my research. Basically, I used the normal PKGBUILD for this package but added "debug !strip" into the options.įortunately. I've setup a debugging-enabled glib2 package based on the Arch wiki link found through your link. At the moment I'm on a fully updated Arch system with this glib2: local/glib2 2.56.0+7+g66948ae23-1 I don't have a cached version of 2.54.4, but it's possible that I delayed updating this machine and 2.56.0 was released during that time. I just noticed this issue and found that bug report from January it explains my exact symptoms and the stack traces are very similar at a glance. Unfortunately, yes I seemed to have the same issue as reported with 2.56.0 installed.
0 kommentar(er)
