From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29582-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 18306 invoked by alias); 7 Sep 2007 18:18:47 -0000
Received: (qmail 18293 invoked by uid 22791); 7 Sep 2007 18:18:47 -0000
X-Spam-Check-By: sourceware.org
Received: from heller.inter.net.il (HELO heller.inter.net.il) (213.8.233.23)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Sep 2007 18:18:42 +0000
Received: from HOME-C4E4A596F7 (IGLD-80-230-13-121.inter.net.il [80.230.13.121]) 	by heller.inter.net.il (MOS 3.7.3a-GA) 	with ESMTP id DOJ57888 (AUTH halo1); 	Fri, 7 Sep 2007 21:18:33 +0300 (IDT)
Date: Fri, 07 Sep 2007 18:24:00 -0000
Message-Id: <u642mtk3p.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
CC: ghost@cs.msu.su, nickrob@snap.net.nz, gdb@sources.redhat.com
In-reply-to: <20070907180548.GA5595@caradoc.them.org> (message from Daniel 	Jacobowitz on Fri, 7 Sep 2007 14:05:48 -0400)
Subject: Re: MI: "^running" issues
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <200709041653.22357.ghost@cs.msu.su> <ud4wuuc7l.fsf@gnu.org> <18145.5117.427647.382269@kahikatea.snap.net.nz> <200709071404.14065.ghost@cs.msu.su> <u8x7itl55.fsf@gnu.org> <20070907180548.GA5595@caradoc.them.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-09/txt/msg00085.txt.bz2

> Date: Fri, 7 Sep 2007 14:05:48 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <ghost@cs.msu.su>, nickrob@snap.net.nz,
> 	gdb@sources.redhat.com
> 
> We ask for more information than we've got in this case, though.

I don't think we do, not in all cases, anyway.

> And you try to get internals chapters written for things like this
> :-)

Yes.  But I can hardly say I succeed, given the current shape of
gdbint.texinfo.  And unfortunately I cannot say I get too much
community support for this Quixotic battle, either.  So my internal
sense of justice does not let me demand Nick (or anyone else who knows
something about the async mode) to produce more design info than we
ask from others, as a prerequisite for accepting patches.

> We're in a tricky situation.

Yes.  But I'm not yet ready to give up and agree to ripping the async
mode out of GDB.