PostgreSQL: Bad system call

Markus Hoenicka
Thu Dec 9 15:51:00 GMT 2004

Reini Urban <> was heard to say:

> The cause is that the internal cygserver msg buffer is allocated
> read-only. (IsBadWritePtr() fails)
> Reason unknown. gcc? cygwin?
> Solution pending.
> Szteps to reproduce:
> cygserver &
> ipcs
> => Bad system call

Oh great. I'm afraid fixing this is above my head. But at least I'd like to help
track down the culprit. The interesting fact is that I've downgraded all
relevant packages that I can think of (PostgreSQL, cygwin1.dll), rebooted the
box, stopped  cygserver, but still get the error. How can I hose a Cygwin
installation that not even downgrading helps? What is it that I did not
downgrade that causes the problem? Does setup.exe keep a log of what I
precisely up/downgraded?

I do like PostgreSQL on Unix a lot, but I really hate to ever touch setup.exe
because more often than not I'm left with a broken database engine.


Markus Hoenicka
(Spam-protected email: replace the quadrupeds with "mhoenicka")

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list