Comment # 4 on bug 1193141 from Dirk Stoecker

Hmm, still an upstream issue, but harder to describe to them. I have no aarch
system, so I can't help directly.

My suggestion would be:
* branch the package to your home
* cause build of debugsource and debuginfo packages (%debug_package macro)
* install all three
* start in gdb, some useful commands:
  * use "up" command until you're inside the program code
  * there is also a command to show the full call stack)
  * "p variable" to print variable, "p *variable" to print pointer contents
* you should get information about the place where the program crashs
* If that happens, but is little helpful try adding "-O0" to CFLAGS
* check if it still crashs - if it does, gdb output should be more to the
point.

If this helps to find the issue provide a patch, if not please share the
details you find, maybe I can help to get the reason.