GNU bug report logs - #52222
27.2; invalid formatting in edebug-set-consitional-breakpoint interactive history

Previous Next

Full log

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

From: Петров Андрей <an.petrov <at> pay-lab.ru>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: "52222 <at> debbugs.gnu.org" <52222 <at> debbugs.gnu.org>
Subject: Re: bug#52222: 27.2; invalid formatting in
 edebug-set-consitional-breakpoint interactive history
Date: Wed, 1 Dec 2021 15:54:36 +0000

[Message part 1 (text/plain, inline)]

Hello, Michael.

I described the problem incorrecty. Here is a screenshot.
Last time I set breakpoint  condition (equal x "String string")
The history is ok.

Andrey.


________________________________________
От: Michael Heerdegen <michael_heerdegen <at> web.de>
Отправлено: 1 декабря 2021 г. 20:08:18
Кому: Петров Андрей
Копия: 52222 <at> debbugs.gnu.org
Тема: Re: bug#52222: 27.2; invalid formatting in edebug-set-consitional-breakpoint interactive history

Петров Андрей <an.petrov <at> pay-lab.ru> writes:

> 1. Instrument some function for debugging
> 2. Goto any line inside that function and set conditional breakpoint using strings in expression:
>   M-x edebug-set-conditional-breakpoint RET (equal some-var "SomeString") RET
> 3. Set a conditional breakpoint again using interactive history:
>  M-x edebug-set-conditional-breakpoint RET [up]
>  I see
>     (equal some-var SomeString)
>  i.e. SomeString turned into a symbol instead of string.

I don't see that - I tested with 27.1 and master.

What I do see is that the confirmation message of edebug looks like the
above (which is a bug) - but only that: the items in the history are
correct.

Michael.

[arch-screen.png (image/png, attachment)]

Previous Next

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