When running the debugger "set stop-on-solib-events 1" is invoked and the debugger is stopped on solib event

Type: Debugger
Input information below

Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.

Describe the bug

• OS and Version: Debian 4.9.18-1
• VS Code Version: 1.30.2
• C/C++ Extension Version: 0.21.0
• Other extensions you installed (and if the issue persists after disabling them):
• A clear and concise description of what the bug is.

I can't attach the logs due to company restriction but I can tell you that when enabling the logger with "engineLogging" I can see that

1: (2569) <-1006-gdb-set stop-on-solib-events 1

and after a while:

1: (7067) ->~"Stopped due to shared library event (no libraries added or removed)\n"
1: (7067) ->*stopped,reason="solib-event",thread-id="1",stopped-threads="all",core="7"
Stopped due to shared library event (no libraries added or removed)

This is happening also if I explicitly add a setup command for disabling the "stop-on-solib-events", in that case I first see the "gdb-set stop-on-solib-events 0" is invoked and then the "gdb-set stop-on-solib-events 1" is invoked (and overrides the first command)

I removed all .initgdb files, and also tried to run gdb with "-nx" arg to eliminate any use of config files, where do these config are coming from and how to edit them?