using O_WRONLY | O_CREAT | O_TRUNC crashes otf2 when iterating through events, trace still get generated -> Python Binding Bug
because creat(fd, mode) == open(path, O_WRONLY|O_CREAT|O_TRUNC, mode) creat is not working (see first in list)
O_DSYNC crashes otf2 -> Python Binding Bug
using O_EXCL and O_CREAT does not produce an otf2 IoCreateHandle event -> Python + otf2-print vllt. scorep?
using two different flags from the same category like O_APPEND | O_NONBLOCK crashes otf2 or O_NOCTTY | O_CREAT -> Python Binding Bug
Score-P Issues
using O_RSYNC or O_SYNC appears to do nothing
O_DIRECTORY does nothing and prevents that a IoCreateHandle event is generated -> otf2-print
calling open(fd, mode); mode ∈ {O_RDONLY, O_WRONLY, O_RDWR, O_WRONLY} without another flag wont create a IoCreateHandle event
fopen created two IoCreateHandle events, script currently only creates one
fopen a, a+ are indifferent from the others -> CreationFlag wird in otf2 nicht gesetzt
getcwd, ..., mknodat, and others even dont show up even if they should in my opinion -> erzeugen keine records in otf2 aber recorder
dup/dup2 dont create a IoDuplicateHandle event in otf2 Why ? -> erzeugt in otf2 nur enter und leave
Recorder Issues
offset tracking not working because tracking the right file handle is not always possible (file can be opened two times by different processes -> same file name but different handle)
different sizes in writev/readv struct can only be approximated
fsync, fdatasync not showing up in recorder
Interessant aber unwichtig
mmap not showing up in recorder or otf2 -> is ok never mind
__O_LARGEFILE not implemented in otf2 -> Interessant aber erstmal nicht so wichtig.