From: Jason Molenda <jmolenda@apple.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC patch mi-cmds.c table format (pedantic)
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <2124EB3A-7912-11D8-A2F0-000393D457E2@apple.com> (raw)
In-Reply-To: <uptba7l9n.fsf@elta.co.il>
Hi Eli,
On Mar 17, 2004, at 9:54 PM, Eli Zaretskii wrote:
>> - { "break-insert", { NULL, 0 }, 0, mi_cmd_break_insert},
>> + { "break-insert", { NULL, 0 }, NULL, mi_cmd_break_insert},
>>
>> - { "exec-step", { NULL, 0 }, mi_cmd_exec_step},
>> + { "exec-step", { NULL, 0 }, mi_cmd_exec_step, NULL},
>>
>> - { NULL, }
>> + { NULL, { NULL, 0 }, NULL, NULL}
>
> Don't these changes require changes to the GDB/MI documentation in
> gdb.texinfo? IIRC, there are examples there to what each command
> outputs.
No, with each of these changes the same code is generated by the
compiler.
J
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jmolenda@apple.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC patch mi-cmds.c table format (pedantic)
Date: Thu, 18 Mar 2004 19:26:00 -0000 [thread overview]
Message-ID: <2124EB3A-7912-11D8-A2F0-000393D457E2@apple.com> (raw)
Message-ID: <20040318192600.R220eJVV8YHcVWAHZ7jizDDB4l5vQ0ptGI29yP7X25A@z> (raw)
In-Reply-To: <uptba7l9n.fsf@elta.co.il>
Hi Eli,
On Mar 17, 2004, at 9:54 PM, Eli Zaretskii wrote:
>> - { "break-insert", { NULL, 0 }, 0, mi_cmd_break_insert},
>> + { "break-insert", { NULL, 0 }, NULL, mi_cmd_break_insert},
>>
>> - { "exec-step", { NULL, 0 }, mi_cmd_exec_step},
>> + { "exec-step", { NULL, 0 }, mi_cmd_exec_step, NULL},
>>
>> - { NULL, }
>> + { NULL, { NULL, 0 }, NULL, NULL}
>
> Don't these changes require changes to the GDB/MI documentation in
> gdb.texinfo? IIRC, there are examples there to what each command
> outputs.
No, with each of these changes the same code is generated by the
compiler.
J
next prev parent reply other threads:[~2004-03-18 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Jason Molenda
2004-03-17 23:47 ` Jason Molenda
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 5:53 ` Eli Zaretskii
2004-03-19 0:09 ` Jason Molenda [this message]
2004-03-18 19:26 ` Jason Molenda
2004-03-19 14:36 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:34 ` Jason Molenda
2004-03-19 15:12 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2124EB3A-7912-11D8-A2F0-000393D457E2@apple.com \
--to=jmolenda@apple.com \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox