From: deivid.rodriguez@...
Date: 2014-06-25T13:29:53+00:00
Subject: [ruby-core:63325] [ruby-trunk - Bug #9937] Segfault in the	TracePoint API

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


Bump!

Similar update: after latest bug fixes in the API (#9957, #9959, #9961, #9964), the build still segfaults in the same place.

By the way, thanks for all the recent work and bug fixes in the TracePoint API!!

----------------------------------------
Bug #9937: Segfault in the TracePoint API
https://bugs.ruby-lang.org/issues/9937#change-47373

* Author: David Rodr��guez
* Status: Open
* Priority: Normal
* Assignee: Koichi Sasada
* Category: 
* Target version: 
* ruby -v: ruby 2.2.0dev (2014-06-12 trunk 46413) [i686-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
Hi!

It seems that a regression bug has been recently introduced in the TracePoint API (maybe after changeset r45758). byebug's test suite works against 2.0 and 2.1, but segfaults against ruby-head. See https://travis-ci.org/deivid-rodriguez/byebug

Segfault occurs in https://github.com/deivid-rodriguez/byebug/blob/master/ext/byebug/byebug.c#L252, I'm guessing the method ID provided by the TracePoint API is nil, so the SYM2ID call fails.

I'm sorry I'm not currently able to properly investigate this.



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