Bug 10389 - script field of -break-info uses braces instead of brackets, violating MI syntax
Summary: script field of -break-info uses braces instead of brackets, violating MI syntax
Status: RESOLVED DUPLICATE of bug 9659
Alias: None
Product: gdb
Classification: Unclassified
Component: mi (show other bugs)
Version: unknown
: P2 minor
Target Milestone: 6.8
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-14 10:12 UTC by Dmitry Dzhus
Modified: 2009-07-14 12:48 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Dzhus 2009-07-14 10:12:28 UTC
When GDB/MI includes script information in `-break-info`, it violates
its own syntax by wrapping script field value in curly braces (like
for tuples) instead of brackets (like for lists, which should be the
case for script listing), for example:

script={"silent","xgetptr Vinitial_window_system","set $tem = ( struct
Lisp_Symbol *) $ptr","xgetptr $tem->xname","set $tem = (struct
Lisp_String *) $ptr","set $tem = (char *) $tem->data","if $tem[0] ==
'x' && $tem[1] == '\0'","break x_error_quitter","end","continue"}

Whereas according to GDB/MI Output Syntax tuples (enclosed in {}) may
contain only variable=value pairs.

In Emacs, I just replace braces with brackets and parse it like a list.
Not a serious bug, just a nuisance.
Comment 1 Dmitry Dzhus 2009-07-14 12:48:48 UTC

*** This bug has been marked as a duplicate of 9659 ***