[#59462] [ruby-trunk - Bug #9342][Open] [PATCH] SizedQueue#clear does not notify waiting threads in Ruby 1.9.3 — "jsc (Justin Collins)" <redmine@...>

9 messages 2014/01/02

[#59466] [ruby-trunk - Bug #9343][Open] [PATCH] SizedQueue#max= wakes up waiters properly — "normalperson (Eric Wong)" <normalperson@...>

11 messages 2014/01/02

[#59498] [ruby-trunk - Bug #9352][Open] [BUG] rb_sys_fail_str(connect(2) for [fe80::1%lo0]:3000) - errno == 0 — "kain (Claudio Poli)" <claudio@...>

10 messages 2014/01/03

[#59516] [ruby-trunk - Bug #9356][Open] TCPSocket.new does not seem to handle INTR — "charliesome (Charlie Somerville)" <charliesome@...>

48 messages 2014/01/03

[#59538] [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — "shyouhei (Shyouhei Urabe)" <shyouhei@...>

33 messages 2014/01/03
[#59582] Re: [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — SASADA Koichi <ko1@...> 2014/01/06

Intersting challenge.

[#59541] Re: [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — Eric Wong <normalperson@...> 2014/01/04

Hi, I noticed a trivial typo in array.c, and it fails building struct.c

[#59583] [ruby-trunk - Bug #9367][Open] REXML::XmlDecl doesn't use user specified quotes — "bearmini (Takashi Oguma)" <bear.mini@...>

12 messages 2014/01/06

[#59642] [ruby-trunk - Bug #9384][Open] Segfault in ruby 2.1.0p0 — "cbliard (Christophe Bliard)" <christophe.bliard@...>

11 messages 2014/01/08

[#59791] About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...>

A while ago I created a proof-of-concept that I intended to use in my

16 messages 2014/01/15
[#59794] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/15

On 15 Jan 2014, at 11:58, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[#59808] Re: About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2014/01/16

Em 15-01-2014 19:42, Eric Hodel escreveu:

[#59810] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/16

On 16 Jan 2014, at 02:15, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[#59826] Re: About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2014/01/17

Em 16-01-2014 19:43, Eric Hodel escreveu:

[#59832] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/17

On 17 Jan 2014, at 04:22, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[ruby-core:59528] Re: [ruby-trunk - Bug #9357] TracePoint's c_return traces return from call to 'trace'

From: Anuj Dutta <dutta.anuj@...>
Date: 2014-01-03 14:49:44 UTC
List: ruby-core #59528
Makes sense.

Thanks.

Will close this now.



On 3 January 2014 14:42, deivid (David Rodr刕uez) <
deivid.rodriguez@gmail.com> wrote:

>
> Issue #9357 has been updated by deivid (David Rodr刕uez).
>
>
> Yes, because tracing is enabled after the 'c_call' and before the
> 'c_return' event.
> ----------------------------------------
> Bug #9357: TracePoint's c_return traces return from call to 'trace'
> https://bugs.ruby-lang.org/issues/9357#change-44067
>
> Author: andhapp (Anuj Dutta)
> Status: Open
> Priority: Normal
> Assignee:
> Category:
> Target version:
> ruby -v: 2.1.0
> Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
>
>
> =begin
> Hello,
>
> In TracePoint, trace on 'c_call' doesn't trace the call made to 'trace'
> method, where as trace on 'c_return' does, is this expected behaviour?
>
> Here's the code I used to reproduce it:
>
> === Code (c_return)
>     class Car
>       def self.start
>         print "Started..."
>       end
>     end
>
>     TracePoint.trace(:c_return) do |tp|
>       puts "'#{tp.event}' event occurred in
> #{tp.defined_class}##{tp.method_id}"
>     end
>
>     Car.start
>
> === Env
>
> Ruby 2.1.0
>
>
> === Actual output
>
>     'c_return' event occurred in #<Class:TracePoint>#trace
>     Started...'c_return' event occurred in IO#write
>     'c_return' event occurred in Kernel#print
>
> === Expected output
>
>     Started...'c_return' event occurred in IO#write
>     'c_return' event occurred in Kernel#print
>
> === Code on eval.in
>
> Here's the link to code on eval.in:
>
> https://eval.in/85264
>
> Thanks.
>
>
> --
> http://bugs.ruby-lang.org/
>



-- 
Anuj DUTTA

In This Thread

Prev Next