From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:69738] [Ruby trunk - Bug #11306] [Third Party's Issue] Segmentation fault
Date: Thu, 25 Jun 2015 10:14:36 +0000 [thread overview]
Message-ID: <redmine.journal-53119.20150625101435.45e1928851136905@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11306.20150625074532@ruby-lang.org
Issue #11306 has been updated by Nobuyoshi Nakada.
Description updated
Status changed from Open to Third Party's Issue
A bug of that gem.
----------------------------------------
Bug #11306: Segmentation fault
https://bugs.ruby-lang.org/issues/11306#change-53119
* Author: David Anderson
* Status: Third Party's Issue
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
bug is detected during CUPS call in cups gem (https://github.com/m0wfo/cups) v0.1.10. The complete core dump is attached as file 'dump.txt'.
the following works okay:
~~~
2.2.1 :001 > list = Cups.show_destinations
=> ["laserjet_1102w", "lp_null"]
2.2.1 :002 > Cups.device_uri_for( list.first )
=> "hp:/net/HP_LaserJet_Professional_P_1102w?ip=192.168.0.65"
2.2.1 :003 > Cups.device_uri_for( list.last )
=> "file:///dev/null"
~~~
the following fails (the order is not important; the second call always fails with abort):
~~~
2.2.1 :001 > list = Cups.show_destinations
=> ["laserjet_1102w", "lp_null"]
2.2.1 :002 > CupsDevice.testit( list.first )
=> "hp:/net/HP_LaserJet_Professional_P_1102w?ip=192.168.0.65"
2.2.1 :003 > CupsDevice.testit( list.last )
/home/daudi/projectspace/swalapala/app/models/cups_device.rb:101: [BUG] Segmentation fault at 0x0000000a491862
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
~~~
where:
~~~ruby
class CupsDevice < ActiveRecord::Base
def self.testit( cups_name )
Cups.device_uri_for( cups_name )
end
end # class CupsDevice
~~~
and in the cups gem:
~~~c
rb_define_singleton_method(rubyCups, "device_uri_for", cups_get_device_uri, 1);
static VALUE cups_get_device_uri(VALUE self, VALUE printer)
{
if (!printer_exists(printer))
{
rb_raise(rb_eRuntimeError, "The printer or destination doesn't exist!");
}
VALUE options_list;
http_t *http;
ipp_t *request;
ipp_t *response;
ipp_attribute_t *attr;
char uri[1024];
char *location;
char *name = RSTRING_PTR(printer);
request = ippNewRequest(IPP_GET_PRINTER_ATTRIBUTES);
httpAssembleURIf(HTTP_URI_CODING_ALL, uri, sizeof(uri), "ipp", NULL, "localhost", 0, "/printers/%s", name);
ippAddString(request, IPP_TAG_OPERATION, IPP_TAG_URI, "printer-uri", NULL, uri);
if ((response = cupsDoRequest(http, request, "/")) != NULL)
{
if((attr = ippFindAttribute(response, "device-uri", IPP_TAG_URI)) != NULL)
{
return rb_str_new2(attr->values[0].string.text);
}
ippDelete(response);
}
return Qtrue;
}
~~~
---Files--------------------------------
dump.txt (206 KB)
cups_device.rb (3.43 KB)
cups.c (14.2 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2015-06-25 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11306.20150625074532@ruby-lang.org>
2015-06-25 7:45 ` [ruby-core:69736] [Ruby trunk - Bug #11306] [Open] Segmentation fault dsaronin
2015-06-25 8:22 ` [ruby-core:69737] " Eric Wong
2015-06-25 10:14 ` nobu [this message]
2015-06-26 1:25 ` [ruby-core:69740] [Ruby trunk - Bug #11306] " dsaronin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-53119.20150625101435.45e1928851136905@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).