From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Denis PILAT <denis.pilat@st.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] -thread-info new command
Date: Wed, 11 Apr 2007 01:16:00 -0000 [thread overview]
Message-ID: <17948.13909.221294.650367@farnswood.snap.net.nz> (raw)
In-Reply-To: <20070410220434.GA8126@caradoc.them.org>
> This is the bit I was talking about, since catch_excepions_with_msg
> requires it be "int" and not "enum gdb_rc".
>
> > do_captured_list_thread_ids (struct ui_out *uiout, void *arg)
> > {
> > ...
> > do_cleanups (cleanup_chain);
> > ui_out_field_int (uiout, "number-of-threads", num);
> > return GDB_RC_OK;
> > }
OK I see now. There still seems to be some kind of mismatch. Perhaps
(sometime) enum return_reason and enum gdb_rc can be harmonised.
>...
> > It would also help stop bugs in front ends from being reported on the gdb
> > mailing list.
>
> Maybe - not if the front end didn't handle it...
Sure. If poeple elect not to use a feature, it won't provide any benefit.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-04-11 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 14:30 Denis PILAT
2007-03-20 1:44 ` Nick Roberts
2007-03-20 3:09 ` Nick Roberts
2007-03-20 3:14 ` Daniel Jacobowitz
2007-03-20 3:26 ` Nick Roberts
2007-03-21 21:09 ` Nick Roberts
2007-03-22 4:35 ` [RFC] gdb_breakpoint " Nick Roberts
2007-03-27 19:54 ` Daniel Jacobowitz
2007-03-27 21:36 ` Nick Roberts
2007-04-04 14:36 ` Denis PILAT
2007-04-10 15:14 ` Daniel Jacobowitz
2007-04-10 14:53 ` Daniel Jacobowitz
2007-04-10 21:54 ` Nick Roberts
2007-04-10 22:04 ` Daniel Jacobowitz
2007-04-11 1:16 ` Nick Roberts [this message]
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=17948.13909.221294.650367@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=denis.pilat@st.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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