From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-14859-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 27833 invoked by alias); 18 Jul 2003 16:12:25 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 27816 invoked from network); 18 Jul 2003 16:12:24 -0000
Received: from unknown (HELO localhost.redhat.com) (66.30.197.194)
  by sources.redhat.com with SMTP; 18 Jul 2003 16:12:24 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 143472B7F; Fri, 18 Jul 2003 12:12:23 -0400 (EDT)
Message-ID: <3F181C66.8030201@redhat.com>
Date: Fri, 18 Jul 2003 16:12:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kris Warkentin <kewarken@qnx.com>,
	Kevin Buettner <kevinb@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: [rfc] Print solib events in mi-mode
References: <062401c34590$97cd09b0$0202040a@catdog> <3F0B315E.7000702@redhat.com> <064e01c34615$0b152ae0$0202040a@catdog> <20030709150847.GA19020@nevyn.them.org> <087801c34630$479de310$0202040a@catdog> <20030709162430.GA20778@nevyn.them.org> <090201c3463f$acc520f0$0202040a@catdog> <1030709174134.ZM2191@localhost.localdomain> <093901c34642$884d0280$0202040a@catdog>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-07/txt/msg00250.txt.bz2


>> > > I picked on solib-svr4 because it's the one normally found lacking.
> 
> At
> 
>> > > least one of the solib backends already does this - probably SOM?
> 
>> >
>> > So you're saying that you're not receptive to this patch but you'd
> 
> consider
> 
>> > a svr4 patch for the load catchpoints?
> 
>>
>> If it could be moved out to solib.c, I'd be receptive to it.  I'm also
>> willing to look at a patch which modifies solib-svr4.c, but I'd prefer
>> one which handles all off the solib backends in one fell swoop.
> 
> 
> The patch is for breakpoint.c.  It's in the print_it_typical() function
> which handles output when a breakpoint is hit.  I'm not sure how I would put
> this into solib.c.

It's also for a different problem.  MIing a few more stop reasons 
wouldn't hurt.

Andrew