GNU bug report logs - #22012
25.1.50; gdb broken by (json-string-format "doesn't start with `\"'!")

Previous Next

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Dmitry Gutov <dgutov <at> yandex.ru>, 22012 <at> debbugs.gnu.org
Subject: bug#22012: 25.1.50; gdb broken by (json-string-format "doesn't start with `\"'!")
Date: Thu, 26 Nov 2015 17:58:22 +0100

>> How would I know what what ‘json-read-string’ tries to read at that
>> moment?  Am I supposed to instrument it?
>
> Why not?

Debugging the debugger while debugging?

> Alternatively...

You mean there's none?

>> Maybe
>>
>>    (unless (char-equal (json-peek) ?\")
>>      (signal 'json-string-format (list "doesn't start with `\"'!")))
>
> ...you can add a (debug) call before (signal ...). And when the debugger hits, press `e' and evaluate (buffer-string) and (point).
>
> Seeing the value of buffer-string might be sufficient if json-read is being called in a wrong buffer.

But what is the use of the above signal when it doesn't tell me where to
find the source of the problem?

>> should report the current buffer and its value of point.
>
> I wouldn't mind if it did. Though that would need to be done in all such places.

Which places?

> But for the purposes of debugging, you can modify just that function's definition to report what's required.

I do so already.  Now it stopped complaining.  Yet another Heisenbug.

>> Anyway, if I understand the backtrace correctly, the current buffer
>> should have been "*breakpoints of emacs.exe*".
>
> I'm not sure what that implies. Does it have JSON content?

What is JSON content?

martin

Previous Next

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