trinity crashed with SIGSEGV in memset avx2_unaligned_erms()

[Francesco Lucarini]

command used:

sudo trinity -a 64 -D -v --ftrace-dump-file out.txt --dangerous

[Francesco Lucarini (apothiphis-z)]

other crash from trinity caught with dmesg

[Francesco Lucarini (apothiphis-z)]

.

[Francesco Lucarini (apothiphis-z)]

.

[Francesco Lucarini (apothiphis-z)]

.

[Francesco Lucarini (apothiphis-z)]

.

[Francesco Lucarini (apothiphis-z)]

This one actually casued to reboot all system and actually changed all system properties like display an so on

[Seth Arnold (seth-arnold)]

Hello Francesco, thanks for the reports. I'm curious about the reboots you found.

Most of these issues are simply due to allocating too much memory. That's normal.

The segfaults are down to abusing the functions and cpu instructions involved. That's normal.

The ELF issues and module issues are defensive programming introduced after tools such as trinity made it easy to find those sorts of flaws. That's normal.

The reboot might be a real problem, or perhaps the OOM-killer simply chose something very important to kill. If you've got notes on how you invoked that run, or could get trinity to emit a reproducer like the syzkaller project does, that might be a finding.

Thanks

[Launchpad Janitor (janitor)]

[Expired for trinity (Ubuntu) because there has been no activity for 60 days.]