Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aborted (core dumped) with LV2 #1203

Closed
fpesari opened this issue Sep 21, 2019 · 7 comments
Closed

Aborted (core dumped) with LV2 #1203

fpesari opened this issue Sep 21, 2019 · 7 comments

Comments

@fpesari
Copy link

fpesari commented Sep 21, 2019

I made an openSUSE package for the LV2 version of Surge and tried on Ardour, it crashes the program.

I then tried with all backends of jalv, it keeps crashing with these errors:

GTK:

GLib-GObject:ERROR:gvaluetypes.c:455:_g_value_types_init: assertion failed: (type == G_TYPE_CHAR)
Aborted (core dumped)

Qt:

*** Error in `jalv.qt5': corrupted double-linked list: 0x0000558a2a86ea30 ***
Aborted (core dumped)
  • Surge Version: 1.6.2
  • LV2
  • 64 bit

My setup:

  • OS: openSUSE Leap 15.1 (GNU/Linux, 64bit)
  • Host Ardour
  • Version 5.12.0
@baconpaul
Copy link
Collaborator

Tagging in @jpcima and @falkTX who worked on the LV2 port in this release.
Thanks for the clear bug report.

@falkTX
Copy link
Contributor

falkTX commented Sep 21, 2019

are you able to get a gdb backtrace?

@fpesari
Copy link
Author

fpesari commented Sep 21, 2019

are you able to get a gdb backtrace?

yes, I will try compiling it with debug symbols and report back

@fpesari
Copy link
Author

fpesari commented Sep 21, 2019

Well, I actually forgot to copy files in /usr/share/Surge, my bad 😆

It was an extreme reaction to that, though! Maybe Surge should warn and exit more gracefully if data files aren't found.

@baconpaul
Copy link
Collaborator

Oh you had the same problem as #1199!

If /usr/share/Surge is missing it pops user dialog saying fix that. That user dialog uses zenity and prints to stderr.

If zenity wasn't installed, though, we core dumped

@falkTX and I fixed that this morning - 77b9cb9

So you should be able to grab master, remove /usr/share/Surge/ and get a non-SEGV but non-crashing surge.

Can you confirm that for us?

@fpesari
Copy link
Author

fpesari commented Sep 22, 2019

Can you confirm that for us?

Confirmed. Much better now! Thank you, also for the speed with which you replied! 😸

@baconpaul
Copy link
Collaborator

Great! We will sweep this fix into a point release this week - closing he issue

Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants