KD sends 0xFFFFFFFF instead of real process ID when loading new shared libraries

While messing around with KDCOM, I discovered this rather unfortunate state of fact.

I'm not sure if we should send the pointer to the PEPROCESS structure, or the proper process ID, hence the jira Issue.