On 8/10/2021 8:58 AM, Roland Roberts wrote:
I have a new, company-supplied Windows 10 laptop, using Cygwin to do
development. I’m having a problem getting XWin to launch apps. XWin
appears to be mostly working normally, meaning if I launch a Cygwin
mintty instance, I can manually set DISPLAY=:0
> And I just confirmed that if I print the context right before NtOpenFile(),
> and just do
> the "continue",
But then I also tried this: I removed the "continue" before "NtOpenFile()" and
allowed it to proceed,
but I moved NtClose(devhdl) right after the "printf" statement (that we were
tweak
> The directory handle is used (indirectly) in NtOpenFile() through the
> attributes, and
> I wonder if that call somehow distorts the internal position within the
> handle, and so
> it restarts from the wrong internal position in the outer loop.
And I just confirmed that if I print the context
> printf ("%5d %5d %9llu sd%c (%lu, %ls)\n",
> 8, (dev_name - 'a') * 16, size >> 10, dev_name,
> (unsigned long) context, dbi->ObjectName.Buffer);
I replaced with this instead (read_bytes added):
printf ("%5d %5d %9llu sd%c (%lu, %ls, %u)\n",
On Aug 18 14:18, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > On second thought, I have a vague idea... Could you please just add
> > something to the output, i.e, change lines 124/125 from
> >
> > printf ("%5d %5d %9llu sd%c\n",
> > 8, (dev_name - 'a') * 16, size >>
> On second thought, I have a vague idea... Could you please just add
> something to the output, i.e, change lines 124/125 from
>
> printf ("%5d %5d %9llu sd%c\n",
> 8, (dev_name - 'a') * 16, size >> 10, dev_name);
>
> to
>
> printf ("%5d %5d %9llu sd%c (%lu)\n",
>
6 matches
Mail list logo
