From: nobu@...
Date: 2019-06-19T00:48:35+00:00
Subject: [ruby-core:93231] [Ruby trunk Bug#15937] Segmentation fault when String#initialize given same string with capacity field

Issue #15937 has been updated by nobu (Nobuyoshi Nakada).


I can't reproduce the buffer corruption nor the segfault, but found the content was cleared on a short string.
Which version did you try?

----------------------------------------
Bug #15937: Segmentation fault when String#initialize given same string with capacity field
https://bugs.ruby-lang.org/issues/15937#change-78681

* Author: luke-gru (Luke Gruber)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Reproduction steps:

string buffer corruption:
```ruby
s = "mystring"
s.__send__(:initialize, s, capacity: 1000)
puts s
```

segfault:

```ruby
s = "mystring that can't be embedded because it's too long and therefore must be allocated"
s.__send__(:initialize, s, capacity: 1000)
```

Thanks for your time :)



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>