➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Odd handling of signal raised if an illegal syscall is attempted on Android
Type: behavior Stage:
Components: C API Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: bup
Priority: normal Keywords:

Created on 2022-02-27 11:26 by bup, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg414148 - (view) Author: Dan Snider (bup) * Date: 2022-02-27 11:26 
On Android, the following calls generate a SIGSYS signal that is neither blocked by pthread_sigmask(SIG_BLOCK, {SIGSYS}) nor ignored after its handler is set to SIG_IGN:

    (os.chroot(path))
    os.setgid(rgid)
    os.setuid(ruid) 
    (os.setegid(gid))
    os.setregid(rgid, egid)
    os.setreuid(ruid, euid)
    os.setresgid(rgid, egid, sgid)
    time.clock_settime(clock, time)
    time.clock_settime_ns(clock, time)
    (socket.sethostname(name))


On the other hand, signal(SIGSYS, lambda s, p: None) will catch the signal, but based on frame it receives (None), I suspect this is a coincidence. Also, the functions with parenthesized names in that list raise the equivalent of OSError(0, "Error", "%s"%args[0]).
History
Date User Action Args
2022-04-11 14:59:56adminsetgithub: 91028
2022-02-27 11:26:00bupcreate