stackprofx 0.2.9 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5268a99f273f914fdce6760bdd997e2df573fab9
-  data.tar.gz: 0322383d93ba46356fa710bfcd0e31f514877e93
+  metadata.gz: e68b8cf2478f6e776337e01d232a6dfce79de54d
+  data.tar.gz: 6536395b81c54d9976de0121815c3c7649e11106
 SHA512:
-  metadata.gz: 67d71b512f6d263e353f55bc2fae79f757894819356c59b26619db1732a58436ab5a9fa0b2a003f2a02e13c378c361843aa6930b4cf68f27f8187de0e83fc811
-  data.tar.gz: d51ef73516992cff4888078314fe409394c109401538c84801c532ad4b1e39a5522dee5a5d493fae912dbd2a6c7c54526ea00bf725e7a2673372ccb62849b8ba
+  metadata.gz: 79aa0a6a6f0998ec1134ba9248f37826037613eb5cf69887dc04952d8576aef6d723b784034db3d768e7d515d6e073ed261a031405814433b1251d7012273593
+  data.tar.gz: 56d170cfec4aa66acae6a7d783d6d3322ce56bf19d7c8e0fad44f0219cdc0d334fb66c3a9b0453bb10bbc618a3d8391d255cb2549b618afd73d32d1019e7dbdb

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    stackprofx (0.2.8)
+    stackprofx (0.2.9)
 
 GEM
   remote: https://rubygems.org/

data/README.md

@@ -10,18 +10,16 @@ should accept.
 I was considering calling it stackprof2, but 2 implies a successor to 1
 and this is in no way "better" than the original project.
 
-[1]: https://github.com/tmm1/stackprof
-
 ### What changes?
 
 `StackProf::run` accepts an options hash to specify profiling parameters.
 Stackprofx adds one more (optional) key: `:threads`. The value for `:threads`
-should be an array of [`Thread`][1] objects to be profiled. All other threads
+should be an array of [`Thread`][2] objects to be profiled. All other threads
 will be ignored.
 
 Even if the `:threads` key is not specified, the behaviour of Stackprofx is
 slightly different. `stackprof` makes use of the `rb_profile_frames()` function
-added to MRI 2.1, but this thread is [limited][2] to only profiling whatever
+added to MRI 2.1, but this thread is [limited][3] to only profiling whatever
 happens to be the "current thread" when the profiling signal is received by
 the Ruby process. Stackprofx will profile every running thread.
 
@@ -30,12 +28,13 @@ To do this, Stackprofx pulls in a bunch of private Ruby headers and reimplements
 (probably will) break in the future, but it's for development, not production,
 right?
 
-[1]: http://ruby-doc.org/core-2.1.5/Thread.html
-[2]: https://bugs.ruby-lang.org/issues/10602
-
 ### TODO
 
 * Investigate terrible hacks required to link against Ruby
 * Make stack deduplication (weights) useful again
 * Less mess
 * Ask someone who knows something about the Ruby GC to review
+
+[1]: https://github.com/tmm1/stackprof
+[2]: http://ruby-doc.org/core-2.1.5/Thread.html
+[3]: https://bugs.ruby-lang.org/issues/10602

data/ext/stackprofx.c

@@ -415,7 +415,7 @@ stackprofx_record_sample_i(st_data_t key, st_data_t val, st_data_t arg)
 
     rb_thread_t *th;
     GetThreadPtr((VALUE)key, th);
-    if (th->status == THREAD_KILLED) return ST_CONTINUE;
+    if (th->status != THREAD_RUNNABLE) return ST_CONTINUE;
 
     num = rb_profile_frames_thread(0, sizeof(_stackprofx.frames_buffer) / sizeof(VALUE), _stackprofx.frames_buffer, _stackprofx.lines_buffer, th);
 

data/stackprofx.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name = 'stackprofx'
-  s.version = '0.2.9'
+  s.version = '0.3.0'
   s.homepage = 'https://github.com/glassechidna/stackprofx'
 
   s.authors = ['Aman Gupta', 'Aidan Steele']

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: stackprofx
 version: !ruby/object:Gem::Version
-  version: 0.2.9
+  version: 0.3.0
 platform: ruby
 authors:
 - Aman Gupta
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-01-23 00:00:00.000000000 Z
+date: 2015-01-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake-compiler