From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10205 invoked by alias); 20 Dec 2001 23:28:27 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 10026 invoked from network); 20 Dec 2001 23:27:08 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 20 Dec 2001 23:27:08 -0000 Received: from porcupine.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id PAA05327 for ; Thu, 20 Dec 2001 15:27:06 -0800 (PST) Received: from porcupine.cygnus.com (law@localhost) by porcupine.cygnus.com (8.11.6/8.11.6) with ESMTP id fBKNQVu27655; Thu, 20 Dec 2001 16:26:32 -0700 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 To: Kevin Buettner cc: Fernando Nasser , gdb-patches@sources.redhat.com Subject: Re: so-thresh.exp problems Reply-To: law@redhat.com From: law@redhat.com In-reply-to: Your message of Thu, 20 Dec 2001 16:06:48 MST. <1011220230648.ZM29801@ocotillo.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Dec 2001 15:28:00 -0000 Message-ID: <27654.1008890791@porcupine.cygnus.com> X-SW-Source: 2001-12/txt/msg00547.txt.bz2 > As one of the solib maintainers, I guess that Jeff's somsolib.c changes > are up to me to approve. I feel kind of funny about this though because > I know almost nothing about this file. It happens ;( As its original author, I've got a pretty good idea about what's going on in somsolib.c -- with the obvious exception of the stuff that came in from HP (such as the solib-limit stuff). > Anyhow, Jeff's somsolib.c change looks okay to me. Also, as far as > I'm concerned, Jeff can check in any other changes that he wants to > make to somsolib.c. Thanks. I don't forsee needing to do any major surgery; most of the problems I'm tripping over are related to the insane ttrace code from HP -- which I doubt anyone outside HP actually understands. > (somsolib.c is one of those files that we want > bring into the solib-*.c fold. Anything that's done to it to put it > into working order first is more than welcome.) Feel free to ask questions if you ever want to start trying to bring it into the fold. Conceptually the code isn't terribly different from the other implementations, but the guts of how we go about getting/setting the information we need is radically different. The joys of SOM. Thanks, jeff