Bug#924448: Debug data! (Was: gimp: Bug#924448: segfault when using measuring tool)

Bernhard Übelacker bernhardu at mailbox.org
Wed Mar 20 12:40:38 GMT 2019


Control: merge 908549 924448



Hello Kingsley,

> It's OK with me if you merge my bug report, #924448, with it.
Ok, I am trying to do so.



> ... why
>     1.) Frederic MASSOT wrote
>             "The fix is built-in for versions 2.10"
>         at
>             https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908549#20
>     2.) but version 2.10.8-2 of debian's gimp
>         package seems to still have the same bug?

Upstream tag 2.10.8 got tagged around 08. Nov 2018.
But that fix got commited at 08. Dec 2018.

Unfortunately no more minor release was done since then.
If a version 2.10.10 would be released, it would contain the fix.



> I'm happy to report your advice elicited a stack
> trace like the one in bug report #908549.
...
> Plus, much as you astutely asked yesterday, yes,
> they do repeat.
> 8 times.

I guess coredumpctl limits the number of frames printed to 64 - to not
spam the system log.

Unfortunately in your log appears following line where I had expected a bt command:

    Undefined command: "".  Try "help".

After the "coredumpctl gdb 20581" you should get a gdb prompt,
there you should be able to issue a bt command.

Also I think there is something wrong with your setup because of these messages,
that may point to binutils/libelf versions, which may be ahead of testing?

    BFD: ...: unable to initialize decompress status for section .debug_aranges




I found I wrote a wrong version in #908549#25:

> The patch might be small enough to be
> cherry-picked to version 2.8 in buster?

That should really be "version 2.10.8".


Kind regards,
Bernhard



More information about the pkg-gnome-maintainers mailing list