2012/10/4 Thomas Faber
> On 2012-10-04 13:07, Christian Costa wrote:
> > 2012/10/4 Paul Chitescu
> >> AFAIK the structure differs for each major version of Windows and some
> SP
> >> too.
> >>
> >>
> > I was expecting something like this. :(
> >
> >
> >> At the minimum I saw some drivers expecti
On 2012-10-04 13:07, Christian Costa wrote:
> 2012/10/4 Paul Chitescu
>> AFAIK the structure differs for each major version of Windows and some SP
>> too.
>>
>>
> I was expecting something like this. :(
>
>
>> At the minimum I saw some drivers expecting that at the returned pointer
>> to be
>> a
2012/10/4 Paul Chitescu
> On Thursday 04 October 2012 08:25:13 am Dmitry Timoshkov wrote:
> > Christian Costa wrote:
> > > PEPROCESS WINAPI IoGetCurrentProcess(void)
> > > {
> > > -FIXME("() stub\n");
> > > -return NULL;
> > > +TRACE("()\n");
> > > +
> > > +/* Return current pr
On Thursday 04 October 2012 08:25:13 am Dmitry Timoshkov wrote:
> Christian Costa wrote:
> > PEPROCESS WINAPI IoGetCurrentProcess(void)
> > {
> > -FIXME("() stub\n");
> > -return NULL;
> > +TRACE("()\n");
> > +
> > +/* Return current process id since PEPROCESS is opaque and drive
Christian Costa wrote:
> PEPROCESS WINAPI IoGetCurrentProcess(void)
> {
> -FIXME("() stub\n");
> -return NULL;
> +TRACE("()\n");
> +
> +/* Return current process id since PEPROCESS is opaque and drivers
> should not access the struct directly */
> +return (PEPROCESS)PsGetCu
