bad system call on HP-UX 10.20

Ralf Hildebrandt R.Hildebrandt at
Fri Mar 24 18:40:32 CET 2000

On Fri, Mar 24, 2000 at 11:17:01AM -0600, David DeSimone wrote:

> > At least I don't get "bad system call" any more.  Nevertheless a
> > program should never crash, but instead throw out an error message.
> The problem is that for some reason, libc implements the system-call
> callout, but the OS does not support the system-call.  The standard
> method for dealing with a bad system-call is to send the process a
> SIGSYS signal, which is what's happening.  The process basically gets
> killed; the "bad system call" message comes from your shell, reporting
> the method that caused the process to die.
> SIGSYS is not one of the signals that GnuPG attempts to catch or handle.

Ok, but since we know that this fails as root on HP-UX (on your box too?),
one could code around this...

Ralf Hildebrandt <R.Hildebrandt at>
If JavaScript is walking alone late at night through a bad part of
town with a pocket full of $20 bills, ActiveX is dropping your
trousers in the middle of the yard of a maximum-security prison,
bending over, and yelling 'Come and get it, boys!' 

More information about the Gnupg-devel mailing list