llnl / llnl/conduit

Errors crash the code when using C interface

Open
#1,374 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
248
Forks
72
Avg merge
1d 16h
Merged PRs (30d)
15

Description

I notice that run-time errors (e.g. trying to open a non-existing file) throw an exception. The C interface doesn't allow catching these exceptions and thus always crash the code.

I am currently examining writing a Julia wrapper https://github.com/eschnett/Conduit.jl using the C interface and this would be a serious problem.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue concerns runtime errors crossing the C interface, with a Julia wrapper as the motivating use case. Trace how an error such as opening a nonexistent file propagates through that interface; the work is done when C callers can handle the failure without an uncaught exception or crash. The payload names no files or tests, so repository exploration is required.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.