avr-run crashes with exit status 139. We confirmed the crash by
re-running it in a fresh debian unstable installation.

The attachment [1] contains a testcase (under ./crash) crashing the
program. It ensures that you can easily reproduce the bug. Additionally,
under ./crash_info/, we include more information about the crash such as
a core dump, the dmesg generated by the crash, and its output.

Regards,
The Mayhem Team (Alexandre Rebert, Thanassis Avgerinos, Sang Kil Cha, David Brumley, Manuel Egele)
Cylab, Carnegie Mellon University

[1] http://www.forallsecure.com/bug-reports/293685d94c4698a7de962f3340e078d8b81534c2/full_report

I have been unable to reproduce this bug on Debian testing using the included
test case. If I run "./crash.sh" then I get the following:

./crash.sh: line 15: warning: command substitution: ignored null byte in input
BFD: Z:1: byte count 1 too small
avr-run: "Z" is not an object file: file format not recognized


And when I run "./crash.sh -g" I get:

gdb: warning: Couldn't determine a path for the index cache directory.
GNU gdb (Debian 13.2-1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/avr-run...
(No debugging symbols found in /usr/bin/avr-run)
(gdb) Undefined command: "AAAAAAAAAAAAAAAAAAAAAAAA".  Try "help".
(gdb) quit

In addition to not being able to get a SEGFAULT I am curious as to why you are
using gdb instead of avr-gdb. I tried with avr-gdb and got the same "Undefined
command" error as with normal gdb.

Please provide more information on this bug if you are able to. Perhaps it was a
bug in upstream gdb that was fixed in a previous release? Or maybe your input
files are not valid?

Thanks
-Steve