The process tab contains information that remains constant over the lifetime of the process, so this is not the appropriate place for current directory information, which can vary. It would have to be part of the event data, but I'm not eager to expand the size of events to add a field that is not commonly used. When would this be useful?
Hello,
Sorry for the very late answer.
The current directory information can be very useful because, some applications (too many IMHO, e.g bat files) rely on it, and have a completely different behavior depending on it. As it may vary over the life time of the process, the current directory at process creation time can be used in the tab page.
Another field that can be useful either in the 'process' tab for the 'Event properties' dialog and 'Process tree' windows is the exit code of the process (the exited time is already displayed)
Thanks.
Have to agree w/ bobie that the working directory will often be manipulated by application integrators and that the working directory can impact an applications behavior. I think it would be uncommon for an application to change its working dir during the life of the process.
So having the the current directory available in the event 'Process Create' (for the father process) and in the event 'Process Start' for the current process can be consistent.
Another data that is often useful are the environment variables both at 'Process Create' and at 'Process start' events.
I have lots of desktop applications that I develop that change the current directory all the time. Just because, in your experience, applications don't change the current directory a lot, doesn't mean that others have the same experience. I would
find this feature extremely useful in trouble-shooting my applications.
