DynamoRIO / DynamoRIO/dynamorio

APP CRASH ffmpeg attach fails with sigtrap

Open
#7,548 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
3.2k
Forks
629
Avg merge
2d 15h
Merged PRs (30d)
31

Description

**Describe the bug**
Attaching drmemtrace to ffmpeg results in a sigtrap.

**To Reproduce**
(CentOS 9)

```console
$ dnf install -y ffmpeg-free
$ wget 'http://download.opencontent.netflix.com.s3.amazonaws.com/ElFuente/Netflix_FoodMarket_4096x2160_60fps_10bit_420.y4m'
$ ffmpeg -y -i Netflix_FoodMarket_4096x2160_60fps_10bit_420.y4m -crf 35 -preset 6 -g 97 -threads 1 -c:v libsvtav1 -f ivf -svtav1-params lp=1 ~/out.bin
$ bin64/drrun -attach $(pgrep -if ffmpeg) -c tools/lib64/release/libdrmemtrace.so -offline
```

ffmpeg crashes with this message:
```
...
Trace/breakpoint trap (core dumped)
```

Please also answer these questions:

* What happens when you run without any client?
_Runs to completion (exit code 0)_

* What happens when you run with debug build ("-debug" flag to drrun/drconfig/drinject)?
```
...
0:00:00.00 bitrate=N/A speed= 0x






<(1+x) Handling our fault in a TRY at 0x00000000712bc3c6>
Trace/breakpoint trap (core dumped)
```

Please provide a symbolized callstack of any crash or assert so we do not have to speculate or guess as to where it is occurring (see our [Linux gdb instructions](https://dynamorio.org/page_debugging.html#autotoc_md146) and [Windows windbg instructions](https://dynamorio.org/page_debugging.html#autotoc_md157) to see how to load DynamoRIO symbols for a callstack).

**Expected behavior**
Generate a trace and not crash the target.

**Versions**
- What version of DynamoRIO are you using? _11.3.0-1_
- Does the latest build from https://github.com/DynamoRIO/dynamorio/releases solve the problem? _This is the latest version._
- What operating system version are you running on? ("Windows 10" is *not* sufficient: give the release number.) _CentOS 9 (kernel v6.13.2)_
- Is your application 32-bit or 64-bit? _64-bit_

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.