This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] -thread-info new command
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: Denis PILAT <denis dot pilat at st dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 11 Apr 2007 13:13:57 +1200
- Subject: Re: [RFC] -thread-info new command
- References: <45FE9E6A.3030906@st.com> <17919.15500.439138.600411@kahikatea.snap.net.nz> <17919.20575.286260.761826@kahikatea.snap.net.nz> <20070320031409.GA7336@caradoc.them.org> <17919.21588.93918.661753@kahikatea.snap.net.nz> <17921.40699.742164.983281@kahikatea.snap.net.nz> <20070327195414.GN28164@caradoc.them.org> <17929.36288.344474.485310@farnswood.snap.net.nz> <20070410145346.GC30086@caradoc.them.org> <17948.1808.87473.108774@farnswood.snap.net.nz> <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