From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 7D96F19C0029 for ; Tue, 20 Oct 2015 03:01:35 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 2B664B5D83E for ; Tue, 20 Oct 2015 03:28:24 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 234AB952408 for ; Tue, 20 Oct 2015 03:28:23 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 5B185120476; Tue, 20 Oct 2015 03:28:21 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with ESMTPS id 7805712041F for ; Tue, 20 Oct 2015 03:28:17 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=PnnNa8L5VK0Jc/rFfBkuK+3Ljks=; b=sKtyGfTKJRtk8hCBJs Jcsc9tcCcfoIORj6AXbYsQEj1Gpjvuaa89ON5kwLQiCTMznEHOSw1rnIFazrS68F 7e+lPejvLD36B5EppmY/R6vmOUM7zgbRZTSn0UGTMF5P2mtdI7DzfaCU0GhKX/Up 7k73hewlOIPvltSc31qY6KTSQ= Received: by filter0855p1mdw1.sendgrid.net with SMTP id filter0855p1mdw1.17356.5625363DD 2015-10-19 18:28:13.171234955 +0000 UTC Received: from herokuapp.com (ec2-54-234-144-244.compute-1.amazonaws.com [54.234.144.244]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id a8_cnsdSS_6eZ2vhA1k-JQ Mon, 19 Oct 2015 18:28:13.030 +0000 (UTC) Date: Mon, 19 Oct 2015 18:28:12 +0000 From: yosy101@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 45743 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11599 X-Redmine-Issue-Author: yosiat X-Redmine-Sender: yosiat 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-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4PAbJrowWmnGF1BXkuaVu59ZAd86Tj4LaXh7 0GnDh/Rz7QIi1wMeTi7G7UAupw0qwWmcO5K+pRc0lvu1AvDPNLHVleMHyltcYn33/iWf5YRlM1yLr2 KiP1MX2gFEGT2CRL/hjOVea38j8jma4F58Bt X-ML-Name: ruby-core X-Mail-Count: 71118 Subject: [ruby-core:71118] [Ruby trunk - Feature #11599] Dump entries of hash in ObjectSpace X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11599 has been updated by Yosi Attias. Nobuyoshi Nakada wrote: > That distinction makes no sense. > Non-special-const objects (including `String`) are always shown in pointer reference form. > That `"0x007f8f3c8baf88"` is the content of a string but not the pointer, then it never appears with your patch. Oh.. I understand what you are saying, I will fix that! Just to make sure I understand your position, you say this distinction is not needed, and in case of this hash: ~~~ str_key = "Hello world".freeze hash = {} hash[:a] = 1 hash[str_key] = -1 ~~~ You want the result to be: ~~~ { "address": "0x007fa3d28c2dc8", "type": "HASH", "class": "0x007fa3d30af400", "size": 2, "entries": [ { "key": ":a", "value": "0x00000000000003" }, { "key": "\"Hello world\"", "value": "0xffffffffffffffff" } ], "references": [ "0x007fa3d28b1230" ], "memsize": 232, "flags": { "wb_protected": true } } ~~~ If so, I have one question: The addresses of the values - "0x00000000000003" / "0xffffffffffffffff", dosen't exist in the dump result - because we don't dump numerics in the dump, and how I can know what is the dump result? Or you want the value logic to be: 1. If this is special const: write the inspected value of it 2. If this is not a special const: write it's address ---------------------------------------- Feature #11599: Dump entries of hash in ObjectSpace https://bugs.ruby-lang.org/issues/11599#change-54486 * Author: Yosi Attias * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Hi, *This is my first c code contribution :)* I am helping developing heap-analyzer (github.com/tenderlove/heap-analyzer), and currently the dumps lacks of "type metadata" information, like: * Hash entries - the keys and value * Array items - the items of the array etc. In the included patch, I have changed the dump of hash to add entries of hash. For example, given the next hash: ~~~ruby hash = { int_key: 1, str_key: "This is my string", inner_hash: { b: 2 } } ~~~ The dump result (ObjectSpace.dump(hash)) will be: ~~~json { "address": "0x007fbc01110340", "type": "HASH", "class": "0x007fbc0109b400", "size": 3, "entries": [ { "is_key_address": false, "key": ":int_key", "is_value_address": false, "value": "1" }, { "is_key_address": false, "key": ":str_key", "is_value_address": true, "value": "0x007fbc01110390" }, { "is_key_address": false, "key": ":inner_hash", "is_value_address": true, "value": "0x007fbc01110368" } ], "references": [ "0x007fbc01110390", "0x007fbc01110368" ], "memsize": 232, "flags": { "wb_protected": true } } ~~~ As you can see, I have the "entries" array, where each entry contains: "is_key_address", "is_value_address" - if the key/value are special consts the inspected value will be printed in the "key"/"value" properties, other their address will be print. Hope you will accept the patch (and I can submit another one for arrays), Yosi. ---Files-------------------------------- objspace_dump_hash_entries.patch (4.8 KB) -- https://bugs.ruby-lang.org/