>Synopsis:      lastcomm(1) shows a memory access violation for every java 
>program executed
>Category:      system amd64 packages
>Environment:
        System      : OpenBSD 7.6
        Details     : OpenBSD 7.6 (GENERIC.MP) #1: Mon Feb 10 00:14:14 MST 2025
r...@syspatch-76-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

        Architecture: OpenBSD.amd64
        Machine     : amd64
>Description:
        On a machine with accounting=YES, /etc/daily shows a
lastcomm(1) report like this:

Purging accounting records:

java[69521]                           -T      username
          __        20.67 secs Fri Feb 28 01:22 (0:00:06.98)
[...]

The -T flag stands for:

           T       The command did a memory access violation detected by a
                   processor trap.

Despite this message, the java program runs successfully and
terminates with an exit code of 0.

>How-To-Repeat:

1. turn accounting on
    # accton /var/account/acct

2. compile and run the test code below (jdk-17.0.14.7.1v0 installed
from packages)
    $ javac Test.java
    $ java Test

3. run lastcomm(1)
     $ lastcomm | grep java

Test.java:

class Test
{
    public static void main(String[] args)
    {
        System.out.println("Test.");
    }
}

>Fix:
        Unknown.  Is this T flag expected from lastcomm(1) for every
java program?

Thanks,
--Kor

Reply via email to