bug#43102: closed ([PATCH] Fix trace-calls-to-procedure)

[GNU bug Tracking System]

Your message dated Wed, 19 May 2021 21:34:26 +0200
with message-id <DC85256C-A247-4986-97DB-6FFD8C9AAC1F@sarc.name>
and subject line Re: bug#48412: duplicate ?
has caused the debbugs.gnu.org bug report #43102,
regarding [PATCH] Fix trace-calls-to-procedure
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
43102: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43102
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [PATCH] Fix trace-calls-to-procedure
>
>
>
>
> Date: 
>
> Sat, 29 Aug 2020 15:26:04 +0100
>
>
>
>
> * module/system/vm/trace.scm: Remove argument
> ---
>  module/system/vm/trace.scm | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/module/system/vm/trace.scm b/module/system/vm/trace.scm
> index e9f17dae8..54840d8fd 100644
> --- a/module/system/vm/trace.scm
> +++ b/module/system/vm/trace.scm
> @@ -73,7 +73,7 @@ trace-calls-to-procedure
>                                     (max-indent (- width 40)))
>    (define (apply-handler frame depth)
>      (print-application frame depth width prefix max-indent))
> -  (define (return-handler frame depth values)
> +  (define (return-handler frame depth)
>      (print-return frame depth width prefix max-indent))
>    (trap-calls-to-procedure proc apply-handler return-handler))
>  
> -- 
> 2.27.0
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#48412: duplicate ?
>
>
>
>
> Date: 
>
> Wed, 19 May 2021 21:34:26 +0200
>
>
>
>
> Patch applied in f9f55b9ce74898d1b0a77dcc9b4aa260e5cd208d. Thanks!
>
>
> > On 16 May 2021, at 09:09, Adriano Peluso <randomlooser@riseup.net> wrote:
> > 
> > Il giorno ven, 14/05/2021 alle 11.13 +0200, Adriano Peluso ha scritto:
> >> I just noticed someone sent a patch that seems relevant here
> >> 
> >> It's in #43102
> >> 
> >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43102
> > 
> > I applied this patch
> > 
> > It does solve the issue, it seems
> > 
> > Now I can tracepoint my procedure
> > 
> > 
> > 
> > 
>
>
>
> --- End Message ---