core dump when progress callback raises an Exception

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, python
Domain
api

Research direction

Start by reproducing the crash through sane.open(...).scan(progress=progress) with a callback that raises an exception, then inspect the C callback handling around Py_DECREF(result). Done means the same callback reports its exception without causing a core dump.

Written by the indexing model from the issue text.

Description

How to reproduce:

!/usr/bin/env python3

import sane

sane.init()

def progress(*args):
    print(args)
    1/0
                                                                                                                                                                  
sane.open(sane.get_devices()[0][0]).scan(progress=progress)

core dump is caused by Py_DECREF(result); with a NULL result

Dominant language
C
Stars
61
Forks
22
No merged PRs in 30d

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.

More from python-pillow/Sane

All issues in python-pillow/Sane

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.