Busted Samples

Open
#45 16 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
c
Domain
embedded-iot

Research direction

Start by locating and running the debug/profiler sample named in the checklist, then determine what is broken and how to reproduce it in the PSP SDK. Update the sample so it works as intended, verify the result, and check off the item once fixed.

Written by the indexing model from the issue text.

Description

Tracking issue for broken samples (of which there are many)
Checking the box indicates the sample has been fixed.
Please comment on this issue rather than filing a separate one for a broken sample.

  • debug/profiler
Dominant language
C
Stars
1.2k
Forks
190
Avg merge
1d 15h
Merged PRs (30d)
12

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 pspdev/pspsdk

All issues in pspdev/pspsdk

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.