From: deivid.rodriguez@...
Date: 2016-12-06T14:12:40+00:00
Subject: [ruby-core:78519] [Ruby trunk Bug#13011] Make `trace_running` an	integer flag again

Issue #13011 has been updated by David Rodr��guez.


Wow, that was fast, thank you Nobu! :)

----------------------------------------
Bug #13011: Make `trace_running` an integer flag again
https://bugs.ruby-lang.org/issues/13011#change-61901

* Author: David Rodr��guez
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.4.0dev (2016-12-06 trunk 56997) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
After https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/55038, byebug's tests started to segfault. See, for example, https://travis-ci.org/deivid-rodriguez/byebug/jobs/130941967.

I investigated a bit and it seems to me that the `trace_running` flag was not suitable to be converted to a bit field (at least not without extra changes), since reverting the changes to that flag fixes the problem.

Find the patch I used attached.

Thanks!

---Files--------------------------------
0001-Make-trace_running-an-integer-flag-again.patch (712 Bytes)


-- 
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>