Talk:Debugging

From ArchWiki
(Redirected from Talk:Step-by-step debugging guide)
Latest comment: 4 July 2023 by Lahwaacz in topic Valgrind and debuginfo

Merge with Debugging/Getting traces

I am commenting on the suggestion of merging this page with the more general page about tracebacks. One of the points of this page is to have a very specific, step-by-step guide to hand to users that has reported bugs (perhaps their first bug report ever). It is not intended to be a comprehensive guide to tracebacks, just the minimum needed steps to get some more useful information. I'm not completely opposed to merging them, but I think they each have different uses and target groups, so I'm leaning towards keeping them separate. Xyproto (talk) 22:51, 29 April 2015 (UTC)Reply[reply]

I'm not fond of the "target group" principle - any article should have a good overview for users unfamiliar to the subject (the article "trunk"), yet provide sufficient details otherwise (the "branches"). Getting this right is challenging, but having one subject in one place pays off in the end, in my view. -- Alad (talk) 07:54, 30 April 2015 (UTC)Reply[reply]
That is a pretty convincing argument! Feel free to merge them if you think it's better that way. --Xyproto (talk) 23:22, 26 June 2015 (UTC)Reply[reply]

Valgrind and debuginfo

As per the discussion at this thread valgrind might need `DEBUGINFOD_URLS="https://debuginfod.archlinux.org"` to be set to work properly under Arch. Probably worth adding it to the relevant section. -- Bluehood (talk)

That variable is automatically set on login via /etc/profile.d/debuginfod.sh, see Debuginfod#Installation. It is also stated multiple times in the thread, while the cases where it "might" be necessary to set the variable manually were never properly clarified. In any case, the behavior of the DEBUGINFOD_URLS variable should be described on the Debuginfod page, not here. — Lahwaacz (talk) 09:27, 4 July 2023 (UTC)Reply[reply]