Looking at the crash reports (e.g. https://errors.ubuntu.com/oops/cac73123-849b-11ee-9b95-fa163ec44ecd) the ProcCmdline look similar:
/usr/bin/gdb --ex file\ "/opt/teamviewer/tv_bin/TeamViewer" --ex core-file\ /tmp/apport_core_b5i0g31o --batch --ex set\ backtrace\ limit\ 2000 -iex set\ debuginfod\ enable\ off --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex print\ __abort_msg->msg --ex p\ -99 --ex print\ __glib_assert_msg --ex p\ -99 --ex print\ (char*)\ __nih_abort_msg --ex p\ -99
So we could try to reproduce crashing with running gdb on TeamViewer.
Looking at the crash reports (e.g. https:/ /errors. ubuntu. com/oops/ cac73123- 849b-11ee- 9b95-fa163ec44e cd) the ProcCmdline look similar:
/usr/bin/gdb --ex file\ "/opt/teamviewe r/tv_bin/ TeamViewer" --ex core-file\ /tmp/apport_ core_b5i0g31o --batch --ex set\ backtrace\ limit\ 2000 -iex set\ debuginfod\ enable\ off --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex print\ __abort_msg->msg --ex p\ -99 --ex print\ __glib_assert_msg --ex p\ -99 --ex print\ (char*)\ __nih_abort_msg --ex p\ -99
So we could try to reproduce crashing with running gdb on TeamViewer.