RFR(M): 8020775: PPC64 (part 12): posix signal printing
goetz.lindenmaier at sap.com
Wed Aug 14 06:27:27 PDT 2013
Yes, it's not all pure posix, but it can be handled the same for all
unixes with some exceptions.
I removed MAX_SIGNAL_NUMBER and could remove two of the APPLE defines.
This leaves 5 pure os-dependencies.
See also my reply to Vladimirs mail and the webrev there.
From: David Holmes [mailto:david.holmes at oracle.com]
Sent: Montag, 29. Juli 2013 04:46
To: Lindenmaier, Goetz
Cc: 'hotspot-dev at openjdk.java.net'; 'ppc-aix-port-dev at openjdk.java.net'; 'Vladimir Kozlov'
Subject: Re: RFR(M): 8020775: PPC64 (part 12): posix signal printing
On 26/07/2013 9:11 AM, Lindenmaier, Goetz wrote:
> we'd like to contribute our posix signal printing.
This really isn't "posix signals" as it combines all the OS specific
signal definitions into one chunk of code.
+ // A number high enough to contain all possible signal numbers.
+ #define MAX_SIGNAL_NUMBER 70
Why do you need this when you use sigaddset to check validity anyway?
What is this "maximum signal number" meant to represent anyway? The
maximum signal number on the platform, or the maximum signal number for
a signal that the JVM will install a handler for?
The runtime team will need to take a good look at this. Personally I'd
rather not see all the different OS stuff piled in together. I'd
certainly like to see as little duplication as possible, but I'd rather
platform specific stuff was dealt with in platform specific files.
> We implemented some routines to print signal and sa_flags information
> in the os/posix files, and call them from
> os::print_siginfo and print_signal_handler() in the various unix
> variant directories.
> The output is a bit more verbose than the existing version.
> We contribute this here, as our aix code uses this too.
> Please review this and test it if you think we should add this.
> We'd appreciate it.
> Thanks and best regards,
More information about the hotspot-dev