Use-after-free in RevLib sendError()

Open
#428 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
java
Domain
backend

Research direction

The report names RevLib's sendError() and a crash following missing status frames, but gives no source file, reproduction steps, or expected behavior. Start by finding sendError() and reviewing the logs from SoCal Showdown that Rev is investigating; use those logs to trace the crash. Done means the use-after-free is understood and the crash can be reproduced and verified as fixed.

Written by the indexing model from the issue text.

Description

REV Robotics

Just tracking this here for CSA visibility. Rev's already looking into logs provided during SoCal Showdown. I believe the timeline was

  1. Missing Status Frames
  2. Crash in sendError()
Dominant language
Java
Stars
195
Forks
26
Avg merge
11h 58m
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wpilibsuite/SystemcoreTesting

All issues in wpilibsuite/SystemcoreTesting

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.