GNU bug report logs - #43102
[PATCH] Fix trace-calls-to-procedure

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 43102 in the body.
You can then email your comments to 43102 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Robin Green <greenrd <at> greenrd.org>
To: bug-guile <at> gnu.org
Cc: Robin Green <greenrd <at> greenrd.org>
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

Message #8 received at 43102 <at> debbugs.gnu.org (full text, mbox):

From: Adriano Peluso <randomlooser <at> riseup.net>
To: 43102 <at> debbugs.gnu.org
Subject: what is this about ?
Date: Sun, 16 May 2021 08:52:38 +0200

Hi

would you give a bit of context ?

What error is this patch supposed to fix ?

Has this anything to do with #48412 ?

https://lists.gnu.org/archive/html/bug-guile/2021-05/msg00033.html

Thanks

Message #11 received at 43102 <at> debbugs.gnu.org (full text, mbox):

From: Adriano Peluso <randomlooser <at> riseup.net>
To: 43102 <at> debbugs.gnu.org
Subject: Re: what is this about ?
Date: Sun, 16 May 2021 09:35:48 +0200

Il giorno dom, 16/05/2021 alle 08.52 +0200, Adriano Peluso ha scritto:
> Hi
> 
> would you give a bit of context ?
> 
> What error is this patch supposed to fix ?
> 
> Has this anything to do with #48412 ?
> 
> https://lists.gnu.org/archive/html/bug-guile/2021-05/msg00033.html
> 
> Thanks


well, I tried your patch and it does fix tracepointing

Thanks !

Message #16 received at 43102-done <at> debbugs.gnu.org (full text, mbox):

From: lloda <lloda <at> sarc.name>
To: randomlooser <at> riseup.net
Cc: 43102-done <at> debbugs.gnu.org, 48412-done <at> debbugs.gnu.org
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 <at> 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
> 
> 
> 
> 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.