[opensuse-packaging] Is there a way to debug exceptions occurring in the %check section in OBS?
Dear all! I have a project where a single test fails with "free(): invalid pointer" running the tests but only in a specific architecture and a specific software environmelnt. I see how that I can use gdb and coredumpctl to debug but I don't see the failing lines. I get: (gdb) bt #0 0xf6fbfec9 in ?? () #1 0x00000000 in ?? () which isn't enough to see where it fails. Is there a way that allows me to debug that problem directly within obs? Best regards -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mai 14 2018, Johannes Weberhofer <jweberhofer@weberhofer.at> wrote:
I see how that I can use gdb and coredumpctl to debug but I don't see the failing lines. I get:
(gdb) bt #0 0xf6fbfec9 in ?? () #1 0x00000000 in ?? ()
which isn't enough to see where it fails.
Try installing all needed debuginfo packages. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
El 14-05-2018 a las 6:54, Johannes Weberhofer escribió:
Dear all!
I have a project where a single test fails with "free(): invalid pointer" running the tests but only in a specific architecture and a specific software environmelnt.
I see how that I can use gdb and coredumpctl to debug but I don't see the failing lines. I get:
(gdb) bt #0 0xf6fbfec9 in ?? () #1 0x00000000 in ?? ()
which isn't enough to see where it fails.
Is there a way that allows me to debug that problem directly within obs?
Best regards
so.. a) adjust your .oscrc extra-pkgs= to include the packages you need for debugging. b) use the --debuginfo flag when osc build c) unfortunately osc build does not have a --install-debug flag that will otherwise become handy for this task.. so.. find out what debuginfo packages are needed and pass them to osc build --extra-pkgs i.e --extra-pkgs="glibc-debuginfo foobar-debuginfo" d) when the build fails.. osc chroot and have fun finding out what's wrong with gdb. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Andreas Schwab -
Cristian Rodríguez -
Johannes Weberhofer