[PATCH 0/1] MR5367: gitlab: Add gdb to the docker images.
I'm currently, very unsuccessfully, tracking down a crash on the unix side that only happens on Gitlab, and although I'm still unable to reproduce it, it then would be useful to have gdb to attach on segfault when I will. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5367
From: Rémi Bernon <rbernon(a)codeweavers.com> --- tools/gitlab/image.docker | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/gitlab/image.docker b/tools/gitlab/image.docker index 4a380dfb51b..143a3f61f8f 100644 --- a/tools/gitlab/image.docker +++ b/tools/gitlab/image.docker @@ -13,7 +13,7 @@ RUN export DEBIAN_FRONTEND=noninteractive; \ dpkg --add-architecture i386 && \ apt-get update && \ apt-get install -y gcc gcc-mingw-w64-x86-64 gcc-mingw-w64-i686 gcc-multilib \ - llvm clang lld \ + gdb llvm clang lld \ git autoconf flex bison perl gettext \ libasound2-dev:amd64 libasound2-dev:i386 \ libcapi20-dev:amd64 libcapi20-dev:i386 \ -- GitLab https://gitlab.winehq.org/wine/wine/-/merge_requests/5367
How are you planning to use gdb? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5367#note_65663
Well I don't actually need it anymore, but still it would be useful in similar occasions. For instance, when SIGSEGV is received for a crash on the unix side, spawn gdb to attach to the process itself and print a backtrace or any other useful information. This could be done for wineserver crashes too. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5367#note_65667
This merge request was closed by Rémi Bernon. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5367
participants (2)
-
Jinoh Kang (@iamahuman) -
Rémi Bernon