Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@allinea.com>
To: Bob Rossi <bob@brasko.net>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: [mi] organize possible exec async mi oc command reasons
Date: Wed, 15 Jun 2005 19:25:00 -0000	[thread overview]
Message-ID: <1118863804.7546.2.camel@cpc4-oxfd5-5-0-cust158.oxfd.cable.ntl.com> (raw)
In-Reply-To: <20050324212036.GB10808@white>

Dear all,

Since this commit, it's now no longer possible to build with ./configure
--disable-gdbmi.  The reason is failure to link because it doesn't find 
async_reason_lookup.

Can I propose we disable that configure option, or are there some
platforms where mi doesn't build?  Patch to follow if we're all in
agreement. 

Regards
David



On Thu, 2005-03-24 at 16:20 -0500, Bob Rossi wrote: 
[..]
> Here is an updated patch, without the testsuite concerns.
> 
> Eli, I hope this doco patch makes more sense, please let me know.
> 
> 2005-03-24  Bob Rossi  <bob@brasko.net>
> 	* Makefile.in (SUBDIR_MI_OBS, SUBDIR_MI_SRCS): Add mi-common.
> 	(gdb/mi/ headers): Add mi_common_h.
> 	(breakpoint.o, infrun.o): Add dependencies mi_common_h.
> 	* breakpoint.c (include): Add include 'mi/mi-common.h'.
> 	(print_it_typical): Use async_reason_lookup.
> 	(watchpoint_check): Ditto.
> 	* infrun.c (include): Add include 'mi/mi-common.h'.
> 	(print_stop_reason): Use async_reason_lookup.
> 
> 2005-03-24  Bob Rossi  <bob@brasko.net>
> 
> 	* gdb.texinfo (GDB/MI Out-of-band Records): Add bullet enumerating
> 	the possible reasons why an exec async record would be returned to FE.
[..]
-- 
David Lecomber <david@allinea.com>


  parent reply	other threads:[~2005-06-15 19:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 15:46 Bob Rossi
2005-03-24 15:54 ` Daniel Jacobowitz
2005-03-24 16:06 ` Daniel Jacobowitz
2005-03-24 18:47   ` Stan Shebs
2005-03-24 21:20   ` Bob Rossi
2005-03-26 10:43     ` Eli Zaretskii
2005-04-30 19:32     ` Daniel Jacobowitz
2005-05-18  3:29       ` Bob Rossi
2005-05-18  3:34         ` Daniel Jacobowitz
2005-05-18  3:36           ` Bob Rossi
2005-05-18  3:43             ` Daniel Jacobowitz
2005-05-18  4:00               ` Bob Rossi
2005-05-18  8:53       ` Bob Rossi
2005-05-26  2:35         ` Bob Rossi
2005-05-28 18:56         ` Daniel Jacobowitz
2005-05-29  2:55           ` Bob Rossi
2005-05-29  3:00             ` Bob Rossi
2005-05-29  4:57               ` Daniel Jacobowitz
2005-05-29  5:53                 ` Bob Rossi
2005-05-29  3:11             ` Daniel Jacobowitz
2005-06-15 19:25     ` David Lecomber [this message]
2005-06-15 20:03       ` Bob Rossi
2005-06-15 20:46         ` Daniel Jacobowitz
2005-03-24 20:00 ` Eli Zaretskii
2005-03-24 21:02   ` Bob Rossi
2005-03-26 10:40     ` Eli Zaretskii
2005-03-26 13:32       ` Eli Zaretskii
2005-03-27  2:56         ` Bob Rossi
2005-03-27  4:42           ` Eli Zaretskii

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=1118863804.7546.2.camel@cpc4-oxfd5-5-0-cust158.oxfd.cable.ntl.com \
    --to=david@allinea.com \
    --cc=bob@brasko.net \
    --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