From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS24940 94.130.0.0/16 X-Spam-Status: No, score=-2.9 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS, SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 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)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id EED731F4C1 for ; Tue, 29 Nov 2022 14:37:56 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.b="piDSK5KB"; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 6E5D27E822; Tue, 29 Nov 2022 14:37:49 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; 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=piDSK5KB; dkim-atps=neutral Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 8D75F7E81A for ; Tue, 29 Nov 2022 14:37:45 +0000 (UTC) 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; s=s1; bh=KaYAFoFPh8XmBjrS0hf7jgYG5rwOquV6CDc367Eh3to=; b=piDSK5KB1UsFwJZNNiduG6TGQNetaMF3IQJ1jlFJ4v5XJwBQyiEfTjszU6QneGUGY0M7 HHYVVvmQRJ5a72TQfDxdIH557N7Jfzm6h33qP0sitG2sEyHz+kv8PpnJGHnt5eEFTquBv2 8S7FD5BsSFPdv0/t3Z9HHmz0uX+5aC5hXz9P4mcOykeZhJ9pbw4ibsdMwt3mPuSMHoQjkh 3TgT935ieP90AXNLbRJAOy89QD5NzGPbgnhGaUuEjyPS7x+Mmr7yB7ucpLZEMOmCKtiCcK rurxm7c8kh3spozB7kqTH00wVkVSKtSyGO7mhtBcfWy5gxY5VuMN9zTdBxQTf72g== Received: by filterdrecv-69c5db5cf4-9z8q7 with SMTP id filterdrecv-69c5db5cf4-9z8q7-1-63861937-39 2022-11-29 14:37:43.998123253 +0000 UTC m=+1006176.513994599 Received: from herokuapp.com (unknown) by geopod-ismtpd-6-4 (SG) with ESMTP id FpOM_OymSMiHCHwYIJOTlA for ; Tue, 29 Nov 2022 14:37:43.914 +0000 (UTC) Date: Tue, 29 Nov 2022 14:37:44 +0000 (UTC) From: mk Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 19156 X-Redmine-Issue-Author: mk X-Redmine-Sender: mk 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: 87413 X-SG-EID: =?us-ascii?Q?f0yYLXlH7VRy6fm3UiLXj7JUFayaJJuLpVxMjU+wUvVPg+ltjslq43HEXlM1Ui?= =?us-ascii?Q?jX+qAGuPS7JQYVIfyZKxJ=2FC6L=2Fq0OX07V4VJge+?= =?us-ascii?Q?UYee1S21pPN6F4aCRW9efGjeQbrKkIEh2pjddAM?= =?us-ascii?Q?AWCjoKJMB0=2FuCBV3+dCKuzwSzHwxmwRvwrX8c98?= =?us-ascii?Q?IBI8NK+jId0Mwd4=2F9MpIk7+6UnpCp+OgG=2F8XLF7?= =?us-ascii?Q?gUTW+=2FKVNEYo6LTexHBQ8WLu6QKqZ1UeGCJRjLS?= =?us-ascii?Q?c0ZAfOTBMx2GG2DUxAKbA=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: 6IWNNIIMGLUE42VFUYEFKHPO26UQIMTQ X-Message-ID-Hash: 6IWNNIIMGLUE42VFUYEFKHPO26UQIMTQ 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:111063] [Ruby master Bug#19156] ObjectSpace.dump_all segfault during string inspection List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Issue #19156 has been updated by mk (Matthias K=E4ppler). It looks like I can't do anything useful with that address: ``` (gdb) p *0x7fced23f4000 Cannot access memory at address 0x7fced23f4000 ``` This is getting mysterious. I looked at process maps to see what kind of me= mory region this is, and it looks like it's a memory-mapped file from `prom= etheus-client-mmap`: ``` pmap -x 216 ... 00007fced23f3000 4 4 0 rw-s- gauge_max_puma_0-0.db 00007fced23f5000 4 4 0 r---- wait.so ... ``` I also cannot dump this region, but I can print the value for the object st= arting at `0x...3000`: ``` (gdb) dump memory /tmp/memdmp 0x7fced23f3000 0x7fced23f5000 Cannot access memory at address 0x7fced23f4000 ``` but: ``` (gdb) p *0x7fced23f3000 $1 =3D 104 ``` That doesn't tell me anything, but I know this library uses a binary format= to serialize metric samples into JSON strings from Ruby hashes using a C e= xtension. The only Ruby strings in here are metric names and labels IIRC. I will investigate more in this direction. It indeed does sound like it is = not strictly a bug with MRI, though I wonder if it should be more resilient= to these kind of rogue objects and just filter them out? ---------------------------------------- Bug #19156: ObjectSpace.dump_all segfault during string inspection https://bugs.ruby-lang.org/issues/19156#change-100323 * Author: mk (Matthias K=E4ppler) * Status: Open * Priority: Normal * ruby -v: ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- I am working on a feature that would allow our application to capture heap = dumps during shutdown for later inspection. These heap dumps are captured via `ObjectSpace.dump_all(output: io)`. While= walking the object space, MRI occasionally segfaults while inspecting stri= ng objects in `search_nonascii` of `string.c`: ``` /usr/local/lib/ruby/3.0.0/objspace.rb:87: [BUG] Segmentation fault at 0x000= 07efee4201000 ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux] ... -- Control frame information ----------------------------------------------- c:0053 p:---- s:0312 e:000311 CFUNC :_dump_all c:0052 p:0130 s:0305 e:000304 METHOD /usr/local/lib/ruby/3.0.0/objspace.rb:= 87 c:0051 p:0023 s:0295 e:000294 METHOD /home/git/gitlab/lib/gitlab/memory/rep= orts/heap_dump.rb:26 ... -- C level backtrace information ------------------------------------------- /usr/local/lib/libruby.so.3.0(rb_print_backtrace+0x11) [0x7efee4ad0c5e] vm_= dump.c:758 /usr/local/lib/libruby.so.3.0(rb_vm_bugreport) vm_dump.c:998 /usr/local/lib/libruby.so.3.0(rb_bug_for_fatal_signal+0xf8) [0x7efee48d0b08= ] error.c:787 /usr/local/lib/libruby.so.3.0(sigsegv+0x55) [0x7efee4a23db5] signal.c:963 /lib/x86_64-linux-gnu/libpthread.so.0(__restore_rt+0x0) [0x7efee4f12140] ..= /sysdeps/pthread/funlockfile.c:28 /usr/local/lib/libruby.so.3.0(search_nonascii+0x30) [0x7efee4a3ca60] string= .c:552 /usr/local/lib/libruby.so.3.0(coderange_scan) string.c:585 /usr/local/lib/libruby.so.3.0(enc_coderange_scan+0x1b) [0x7efee4a3e28a] str= ing.c:709 /usr/local/lib/libruby.so.3.0(rb_enc_str_coderange) string.c:727 /usr/local/lib/ruby/3.0.0/x86_64-linux/objspace.so(is_broken_string+0x8) [0= x7efeced9c304] ../../internal/string.h:116 /usr/local/lib/ruby/3.0.0/x86_64-linux/objspace.so(dump_object) objspace_du= mp.c:388 /usr/local/lib/ruby/3.0.0/x86_64-linux/objspace.so(heap_i+0x39) [0x7efeced9= caa9] objspace_dump.c:521 /usr/local/lib/libruby.so.3.0(objspace_each_objects_without_setup+0xaf) [0x= 7efee48e878f] gc.c:3232 /usr/local/lib/libruby.so.3.0(objspace_each_objects_protected+0x14) [0x7efe= e48e87c4] gc.c:3242 /usr/local/lib/libruby.so.3.0(rb_ensure+0x12a) [0x7efee48d96aa] eval.c:1162 /usr/local/lib/libruby.so.3.0(objspace_each_objects+0x28) [0x7efee48fb458] = gc.c:3310 /usr/local/lib/libruby.so.3.0(rb_objspace_each_objects) gc.c:3298 /usr/local/lib/ruby/3.0.0/x86_64-linux/objspace.so(objspace_dump_all+0x88) = [0x7efeced9b068] objspace_dump.c:616 ... ``` Unfortunately I couldn't get my hands on that memory region to see which st= rings are causing this since this doesn't always happen. I suspect this is also a problem with MRI master since the code looks uncha= nged from 3.0.4. --=20 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-c= ore.ml.ruby-lang.org/