Getting proper backtrace from GDB

#1

I was trying to get a backtrace log and got this message :

(Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Is the proper way to run the sync option :

./ardour8 --gdb --sync

I still got the same message above when running with --sync. Is that normal ?

logs are here :
Tracker

#2

At the gdb) prompt, instead of typing just “run” type “run --sync”

Almost certainly a plugin drawing from the wrong thread, BTW.

#3

The plugin in question only has a generic GUI.

but the plugin is question is also known to have been incorrectly packaged by Ubuntu, causing crashes.

@Schmitty2005 Can you test with ACE Reverb (comes with Ardour, also has a genericUI), or try with the latest release of the official binary from x42 Zero Config|Latency Convolver

#4 
(gdb) run --sync
Starting program: /usr/bin/env --sync
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
/usr/bin/env: unrecognized option '--sync'
Try '/usr/bin/env --help' for more information.
[Inferior 1 (process 6845) exited with code 0175]
(gdb)

Is there something I need to apt-get ?

#5

No. The script we provide can’t be used to pass --sync to ardour at this time, alas.

#6

Yes, I was able to reproduce the crash using ACE Reverb after three or four attempts. The exact renamed text was ATH-M50x I am thinking the ‘-’ character may be suspect, as I could not get a crash with alpha or numerical characters.

#7

Is that name also in use elsewhere in the session?
Did you manage to get a backtrace?

#8

No.

Not from ACE Reverb, as the --sync option was not working. Would it still be worthwhile to get a backtrace without --sync on ACE REVERB crash ? I can get one if you think it would help.

EDIT: I have added a bt log from ACE Reverb to tracker. without --sync option

EDIT: Also, I had to close the open plugin window before renaming to reproduce crash.

#9

@x42 This seems to be related to Wayland. I could not reproduce on XOrg.

Would it be easy to have Ardour output what video server is being used on gdb logs ? Maybe it already does, and I did not see it.

Wayland seems to have issues on occasion, where as XOrg just works.

#10

I’m not sure about gdb, but Ardour’s could print the env variable $XDG_SESSION_TYPE.

#11

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.