-
Notifications
You must be signed in to change notification settings - Fork 46
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
segmentation fault for transient print on forked process #6
Comments
I'll look into it. I've been rather hands-off lately and the last pull request I merged passed all the tests so assumed things were ok. What version of OS X are you using? |
OSX 10.7 but I had the same issue with 10.6 |
This is either an issue with tempfile instantiation or something more profound in the PrintJob object. It's 11.30 at night here so I'll take a look tomorrow. I hadn't really mentioned it to anybody but I have a limited subset of the gem methods ported to the FFI, if there's interest I'll consider spending some more time on getting something to release. |
I know I keep pressing the wrong button. My bad. |
Thank you for looking in to this. |
I tried using the cupsffi gem and my app segfaults in a very similar way when i reaches cupsGetDests. Could this be a general problem with the cups library? |
On my Rails application cups works perfectly fine but when I set up resque to create workers, for printing, cups gem crashes with a segmentation fault. Here is the output: http://pastie.org/2387372
All other workers are fine and the printing code works fine all the way up to the point that I call Cups::PrintJob::Transient.new and it immediately segfaults. Any help with this would be highly appreciated.
The text was updated successfully, but these errors were encountered: