Well, i have a problem.
I have been building Icinga2 from the sources in my Docker Containers for some time to have a current version. (Alpine currently offers 2.8.0 as the last stable version)
As a basis I use Alpine 3.7.
I’ve been working like this since version 2.8.1 and it’s going pretty well.
When I released my Ruby gem last week as a final 1.0 release, I ran the spec tests against both 2.8.1 and 2.8.2.
With 2.8.1 everything works as intended but with 2.8.2 icinga dies with a segmentation fault as soon as I perform a lot of API calls very quickly.
The Spec Tests have a total of 106 tests and I’ll never make it over 34.
Now I wanted to deliver at least something tangible and yesterday I dealt very intensively with
gdb, but unfortunately I did not understand the whole thing.
Maybe someone will help me with the use of
Here gdb should be able to start icinga automatically and throw a stacktrace (if possible). Alternatively, I modify the container so that I hand icinga over to the gdb.
Before someone reminds me of this, i read it and tried it, but I didn’t succeed.
I can’t and don’t want to open a bug report just because of some obscure suspicion.