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: Tue, 20 Mar 2007 03:26:00 -0000 [thread overview]
Message-ID: <17919.21588.93918.661753@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070320031409.GA7336@caradoc.them.org>
> > It looks like I've misremembered, as the patch I've quoted is for
> > mi_cmd_break_insert and not gdb_thread_select. However, perhaps we should
> > still resolve the issue first.
>
> Yes, I agree. Is that the latest patch posted, if you know offhand?
I had thought it was, but no. You replied with:
http://sourceware.org/ml/gdb-patches/2006-11/msg00185.html:
It seems pretty clear to me that the patch which switched things to
return the result of catch_exceptions_with_msg was wrong. The
functions are defined to return an enum gdb_rc. Can't we make
them do that again? Simple, obviously correct.
but I could only come up with:
http://sourceware.org/ml/gdb-patches/2006-11/msg00208.html
which didn't seem that simple and is probably not correct
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-03-20 3:26 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 [this message]
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
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=17919.21588.93918.661753@kahikatea.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