http://bugs.winehq.org/show_bug.cgi?id=58414
Bug ID: 58414 Summary: winedbg from winehq packages in Fedora 42 crashes during attaching to process. Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs@winehq.org Reporter: bernhardu@mailbox.org Distribution: ---
Created attachment 78829 --> http://bugs.winehq.org/attachment.cgi?id=78829 fedora-42-winehq-devel-10.10-windbg-attach-crash.txt
While investigating bug #58335 I found me getting a crash from winedbg when I tried to attach to some process like winemine.exe.
In function dwarf2_parse_compilation_unit it looks like comp_dir.u.string is allowed to contain NULL because of the assignment in line 3090: 3090 comp_dir.u.string = NULL;
Unfortunately a few lines later this comp_dir.u.string is given to function source_build_path: 3100 tmp = source_build_path(comp_dir.u.string, name.u.string);
But therefore function source_build_path does an unconditional strlen(NULL), which causes a SIGSEGV: 62 unsigned bsz = strlen(base);
http://bugs.winehq.org/show_bug.cgi?id=58414
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Fedora
http://bugs.winehq.org/show_bug.cgi?id=58414
Eric Pouech eric.pouech@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@gmail.com
--- Comment #1 from Eric Pouech eric.pouech@gmail.com --- a quick look at Fedora's ntdll.so debug file show that the AT_comp_dir is present, but has been stored in an external .dwz file
so need to investigate why the strp_alt form isn't correctly working in this case
quick question (may or may not be related): how did you install the debug info packages? - explicitely installed the wine-core-debuginfo package? - did nothing explicit (debuginfod triggered by gdb, lldb... may have filled local debug info) - other
http://bugs.winehq.org/show_bug.cgi?id=58414
--- Comment #2 from Bernhard Übelacker bernhardu@mailbox.org --- (In reply to Eric Pouech from comment #1)
quick question (may or may not be related): how did you install the debug info packages?
- explicitely installed the wine-core-debuginfo package?
- did nothing explicit (debuginfod triggered by gdb, lldb... may have filled
local debug info)
- other
This are my wine related manual dnf calls: $ dnf history list ID Command line 6 dnf install wine-devel-debuginfo-10.10-1.1.x86_64 4 dnf install winehq-devel