WineDbg: Remove Additional Current Process Tracking in backtrace_all

[Robert Shearman]

Hi,

Previously, the code had a danger of accessing freed memory due to the 
fact that cp can be freed during dbg_detach_process. This caused access 
violations during "bt all" commands under certain circumstances with 
non-trivial programs (multiple processes and threads). I did not try to 
find the specific code path that caused the problem 
(dbg_curr_process->imageName being 0xc), but removed the code with 
incorrect assumptions. Keeping the attached process the same before and 
after running the "bt all" command is not safe at all at the moment due 
to the lack of ref-counting on the processes.

Changelog:
Remove additional current process tracking in backtrace_all as it can 
refer to freed memory.

-- 
Rob Shearman

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winedbg.diff
Type: text/x-patch
Size: 1504 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20050713/0533796e/winedbg.bin