Segmentation fault

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
api

Research direction

Start at the serdes_schema_get entry point and reproduce the failure with a schema that is unavailable, comparing normal execution with gdb or debug=all as described. Done means the call no longer segfaults and consistently reports the expected 404 "Subject not found" response.

Written by the indexing model from the issue text.

Description

I work in C langage.
The serdes_schema_get crash (segmentation fault) is when the schema is not available.
The crash is random and appear 75% of time.
Message when no crash : REST request failed (code 404): {"error_code":40401,"message":"Subject not found."}
When it's bad : Segmentation fault
If i start my program with gdb or if use debug=all, there is no crash

Dominant language
C
Stars
12
Forks
62
PR merge metrics
No merged PRs in 30d

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 confluentinc/libserdes

All issues in confluentinc/libserdes

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.