-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port to a new backend? (was: segfault on OS X Mojave) #5
Comments
I traced what You're calling decodeMultiple(): zxinglight/zxinglight/_zxinglight.cpp Lines 66 to 70 in 6dd20ae
they're only calling that if you pass Indeed, I can reproduce the exact same crash. It's bizarre; I don't read asm that well but it looks like my compiler hard-coded
|
Hi, @kousu. Thanks for opening this issue. At first glance, it looks to me like this is coming from ZXing itself. Unfortunately, I don't use OS X and therefore I'm unable to help you with this one. |
Well, I wrote #6 as a workaround, so when that goes in I'll be happy enough :) And it seems that if I build from source instead of using brew's packages the problem goes away, so the bug isn't with you at all. But it seems that me making a fuss has maybe convinced zxing-cpp to finally give up 😨 , and it got deleted from brew this morning after they'd been thinking about doing it for a while 😭 , so you might be losing your upstream sometime soon. There's a replacement zxing-cpp that @glassechidna recommended with a better API maybe? I also am personally all about this tiny BSD-licensed, pure-C library; it looks like it would be easier to wrap, while maintaining the API. It only works in multimode. |
I've created #7 and I'd prefer to take any further discussion about porting this package to nu-book/zxing-cpp there. Since this issue reports a bug that in fact isn't a bug in this package, I'm closing it. When it comes to porting to other decoder backends, I think it'd be better if somebody came up with another package. This one was designed to be a simple wrapper around ZXing rather than a catch-all multi-backend (bar)code toolkit. |
I'm getting a segfault with zxinglight every time it successfully parses a QR code.
Here's a test script that reproduces the crash:
and an image that triggers it:
and an image that does not trigger it.
It seems that something is glitching on munging the zxing-cpp result back into python.
Here is the backtrace in full gory Apple detail:
It's something specific to zxinglight because the zxing binary can handle this image fine:
Furthermore, this happens for me even with your tests. (yay tests!)
The text was updated successfully, but these errors were encountered: