On Sonntag, 14. November 2021 18:50:13 CET Kolja Koch wrote:
> > There is also "gigdump --verify foo.gig" from the command line BTW
> > (man gigdump).
>
> Good to know, thanks!
>
> > > > You could start by providing the questioned info, plus a backtrace of
> > > > the
> > > > crash.
>
> I've never done that before. Is the attached trace.log what you mean?
> I really can't tell if this is useful to anyone...
>
> Cheers,
> Kolja
You need to compile libgig and gigedit with debugging symbols turned on for
the backtrace to contain the required information like function name, source
file line number, function arguments passed, etc.:
https://bugs.linuxsampler.org/
If you are installing libgig by some distro/package script then also make sure
it does not 'strip' the binaries, otherwise it renders the backtrace output
useless again.
CU
Christian
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
