From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [94.130.110.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 99DF41F44D for ; Tue, 9 Apr 2024 18:53:48 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; secure) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=jPGLP+Bo; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=DomZykeN; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 8A19B84209; Tue, 9 Apr 2024 18:53:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1712688820; bh=e4L2kUDXa+mT1K7Up3b5x881wpgzberzVQeGgNCm6HU=; h=Date:References:To:Reply-To:Subject:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From:Cc:From; b=jPGLP+BoZsfsAzJWDyvyxE5EzbT7jnwtCeQzc6nunY3D/b2lu/YYvctuVTGhmAHcW mzZNzQSk3zqVfyp8nTuXxQWKAifLL124YFP16N862XJl77irRzSs15WXlBWNO9MbJC oG2bImnUgZ57oY+jwUCqK36jGSuiPyMfBl6wUSek= Received: from s.wrqvtzvf.outbound-mail.sendgrid.net (s.wrqvtzvf.outbound-mail.sendgrid.net [149.72.126.143]) by nue.mailmanlists.eu (Postfix) with ESMTPS id A15AA81358 for ; Tue, 9 Apr 2024 18:53:36 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=pass (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=DomZykeN; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=mGsmXx0V2Lz7dOysTNCK1zKzUjch+/Izju1zz5Iec5I=; b=DomZykeNSYm1gf+FCJbt4f66EnoMP69ygSrWRBEjIduvuqxKQaS+Fp/3qTG1RcKwesMN gJGtum6p/PMhpf4YBKtilgo8ZHpvvxp3AU0CGlhdsJFYXOmKUgr8vDQYslJD/QDIshpR/X A+jxHC1LG7T4k1KMQwF3CPiMhP26XAN6yw24w46f2iIMuc0WCUxnh5OGd1yRFTnNwTVpZU gEoTXmgWPl4drmVnZGds3KPfvMboRbyuOFRzCFb4wdyzlWUrqhi3p5wWkLsPKBcT3AUEPy G4QdgGkaGz2vRVFJNsYGOsvWhgVNEwOeJyBlfSFHmFS/BDCDOMwt/4+m7uuYmvqQ== Received: by recvd-d64b65bdd-rbqz4 with SMTP id recvd-d64b65bdd-rbqz4-1-66158EAE-A 2024-04-09 18:53:34.5056715 +0000 UTC m=+420191.997278842 Received: from herokuapp.com (unknown) by geopod-ismtpd-21 (SG) with ESMTP id KhwK_uUVQqGHFYf4HfufCg for ; Tue, 09 Apr 2024 18:53:34.433 +0000 (UTC) Date: Tue, 09 Apr 2024 18:53:34 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 20332 X-Redmine-Issue-Author: praveenrocket X-Redmine-Issue-Priority: Normal X-Redmine-Sender: jeremyevans0 X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 94074 X-SG-EID: =?us-ascii?Q?u001=2ELyyp8a6L4BPdoBZ5kcNQuEdalXgUnCKLcPykf2c9d2sTWfvALBzqM4Ij+?= =?us-ascii?Q?Jg9Prp2eVDkf9lIZhzc05KfUT4Npfgnigb95d+v?= =?us-ascii?Q?hGuAMoCQYcLXoRrWnq1GPW1mtFxmcQLpSjxJ5bk?= =?us-ascii?Q?U5Qep+SmdsgExb0nIatoktwkwMmAbmzKc+DnwjU?= =?us-ascii?Q?1=2Fnlf=2FeGgDr+G8ke+6pu+NmJHl2w41Co+I4BBxo?= =?us-ascii?Q?oUvVhqWacsKCdLsKi6++bSbZb1H6NSVHO2fhPIU?= =?us-ascii?Q?Oeb1OlVe5degY+Qm4yFdBuEUAA=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: UMMAWUQ7UGN5FKIUZL54FUGTB6LEXNJ7 X-Message-ID-Hash: UMMAWUQ7UGN5FKIUZL54FUGTB6LEXNJ7 X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:117479] [Ruby master Bug#20332] After upgrading to ruby v 3.2.3 rb_scan_args() skips argument value List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "jeremyevans0 (Jeremy Evans) via ruby-core" Cc: "jeremyevans0 (Jeremy Evans)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20332 has been updated by jeremyevans0 (Jeremy Evans). Status changed from Open to Feedback Can you please provide a self contained example that does not require the ibm_db gem? Otherwise, I'm not sure we'll be able to debug this. ---------------------------------------- Bug #20332: After upgrading to ruby v 3.2.3 rb_scan_args() skips argument value https://bugs.ruby-lang.org/issues/20332#change-107866 * Author: praveenrocket (Praveen N) * Status: Feedback * ruby -v: 3.2.3 * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Hi, Note: I am not an expert at ruby. I am working on ibm_db gem, its an adapter developed using ruby C extension, which helps ruby & rails applications to connect to DB2 database. Here is a github link for its source https://github.com/ibmdb/ruby-ibmdb/tree/master As of now ibm_db gem is compatible with ruby v 3.1. Now I am trying to make ibm_db gem compatible with ruby v 3.2.3. All my test cases were working for ruby v 3.1, but post upgrading to ruby v 3.2.3, most of my test cases are failing. After debugging using gdb what I see is, my ruby test cases calls ruby C extension API passing required arguments, but inside C extension code arguments are not parsed, indeed nothing is read. Because of this most of test cases are failing. Below is a sample ruby script which when run calls ibm_db extension, ``` ruby $ irb irb(main):001:0> require 'ibm_db' => true irb(main):002:0> conn = IBM_DB.connect("DATABASE=sample;HOSTNAME=waldevdbclnxtst06.dev.rocketsoftware.com;PORT=60000;PROTOCOL=TCPIP;UID=zurbie;PWD=A2m8test;",'','') (irb):2: warning: undefining the allocator of T_DATA class IBM_DB::Connection => # irb(main):003:0> stmt = IBM_DB.exec conn,'create table abc(C1 int)' => false irb(main):004:0> irb(main):005:0> IBM_DB.close(conn) => true irb(main):006:0> exit ``` Above, If you observe IBM_DB.exec is called passing two arguments conn & string with create table query. In extension code https://github.com/ibmdb/ruby-ibmdb/blob/master/IBM_DB_Driver/ibm_db.c, below function will be called ``` c VALUE ibm_db_exec(int argc, VALUE *argv, VALUE self) { .... rb_scan_args(argc, argv, "21", &connection, &stmt, &options); ...... } ``` Note: Please refer https://github.com/ibmdb/ruby-ibmdb/blob/master/IBM_DB_Driver/ibm_db.c for complete code. rb_scan_args used to parse arguments very well in ruby v 3.1, but now its failing to do so. I see stmt parameter doesnt hold anything. I just want to know whats issue here, Am I passing arguments in wrong way (in ruby script), or am I not using rb_scan_args properly ? To reproduce, Install ruby v 3.2.3, Install ibm_db gem version 5.4.1 (latest) Run above sample ruby script using IRB. Response at earliest is much appreciated. Thanks Praveen -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/