Greetings, Hamish MB!
Please no top-posting in this channel.
> Note: I've just realised this only happens when 3D acceleration is
> enabled in VirtualBox, hence this may be a VirtualBox bug, rather than a
> Cygwin bug. Thoughts?
What video mode did you select for your system?
Which driver (stand
On 2019-09-12 11:16, Kaz Kylheku wrote:
So even in light of the goal of Cygwin providing GNU/Linux
compatibility
beyond POSIX, there is no justification for supporting times(0).
What I wrote here is not true; on Linux, this is a system call, which
provides detection of some kinds of bad pointe
On 2019-09-12 12:05, tl...@twcny.rr.com wrote:
> The code below returns -1. It shouldn't.
> #include
> #include
> int main(int argc, char *argv[])
> {
> printf("return value %ld\n", (long)times((struct tms*)0));
> return 0;
> }
It should.
The times(3) function requires a pointer to object st
On 2019-09-12 11:05, tl...@twcny.rr.com wrote:
The code below returns -1. It shouldn't.
Says who?
I don't see anything in the specification which says that a null pointer
argument is allowed:
https://pubs.opengroup.org/onlinepubs/9699919799/functions/times.html
Passing a null pointer to an
The code below returns -1. It shouldn't.
#include
#include
int main(int argc, char *argv[])
{
printf("return value %ld\n", (long)times((struct tms*)0));
return 0;
}
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Docume
On 2019-09-11 23:18, Kaz Kylheku wrote:
> On 2019-09-11 20:59, Brian Inglis wrote:
>> On 2019-09-09 11:13, Petr Skočík wrote:
>>> There's been a twitter discussion on how different POSIX platforms
>>> handle malloc(0): https://twitter.com/sortiecat/status/1170697927804817412 .
>>>
>>> As for Cygwin
On 9/9/2019 1:13 PM, Petr Skočík wrote:
> There's been a twitter discussion on how different POSIX platforms
> handle malloc(0): https://twitter.com/sortiecat/status/1170697927804817412 .
>
> As for Cygwin, the answer appears to be "not well", but this should be
> easy to fix.
Can you show how yo
On 2019-09-12 07:37, Haanraadts, Mark (HBO) via cygwin wrote:
> I have a problem with remote ssh sessions to corporate Red Hat 6 servers and
> X11 forwarding. Xclock works perfectly fine on my local CYGWIn install. On a
> remote server I get:
> $ xclock
> Error: Can't open display:
>
> Here's th
I have a problem with remote ssh sessions to corporate Red Hat 6 servers and
X11 forwarding. Xclock works perfectly fine on my local CYGWIn install. On a
remote server I get:
$ xclock
Error: Can't open display:
Here's the debug shell logfile:
debug2: we sent a password packet, wait for reply
de
Note: I've just realised this only happens when 3D acceleration is
enabled in VirtualBox, hence this may be a VirtualBox bug, rather than a
Cygwin bug. Thoughts?
Hamish
On 12/09/2019 12:33, Hamish McIntyre-Bhatty wrote:
> Okay, so after the latest set of updates, this still seems to happen.
> Att
Okay, so after the latest set of updates, this still seems to happen.
Attached is the XWin.0.log file. I am running this in Virtualbox, so it
is possible that this issue has something to do with that?
Hamish
On 07/09/2019 19:50, Hamish McIntyre-Bhatty wrote:
> I was starting with "startxwin &" in
11 matches
Mail list logo
