GNU bug report logs - #12113
24.0.96; Incorrect echoing of gdb output

Previous Next

Full log

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

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 12113-done <at> debbugs.gnu.org,
 "William M. \(Mike\) Miller" <william.m.miller <at> gmail.com>
Subject: Re: bug#12113: 24.0.96; Incorrect echoing of gdb output
Date: Thu, 31 Oct 2019 00:36:29 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Wed, 1 Aug 2012 13:30:26 -0400
>> From: "William M. (Mike) Miller" <william.m.miller <at> gmail.com>
>> Cc: 12113 <at> debbugs.gnu.org
>> 
>> The real problem is suppressing the output of the parameter
>> values when hitting a breakpoint after running or continuing via
>> a graphical button, or when stepping into a function.  Those values
>> do not appear in the "locals" buffer, so to see them I either have
>> to print them manually or, if it's a breakpoint, I have to set an
>> action list to display them.
>
> In the Breakpoints window, if you click the "Threads" button on the
> window's header line, don't you see the arguments of the current
> function's call?

More information was requested, but none was given within 7 years, so
I'm closing this bug.  If this is still an issue, please reopen the bug
report.

Best regards,
Stefan Kangas

Previous Next

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