From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9831 invoked by alias); 12 Sep 2002 15:40:31 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9824 invoked from network); 12 Sep 2002 15:40:29 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 12 Sep 2002 15:40:29 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 343AD3C8C; Thu, 12 Sep 2002 11:40:27 -0400 (EDT) Message-ID: <3D80B56B.6090601@ges.redhat.com> Date: Thu, 12 Sep 2002 08:40:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: Re: Broken remote protocol qOffsets response handling References: <3D80A114.1060809@agilent.com> <20020912145801.GA3404@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00115.txt.bz2 > On Thu, Sep 12, 2002 at 07:13:40AM -0700, Earl Chew wrote: > >> I started using qOffsets, and was dismayed to find that gdb remote.c >> silently discards bss, and uses data twice instead. >> >> Looking through the archives, I see that jtc has already posted >> a patch to resolve this issue (both in remote.c and nlm/gdbserve.c). >> >> http://sources.redhat.com/ml/gdb-patches/1999-q4/msg00011.html >> >> Apparently nlm/gdbserve.c is the root of the problem (.bss and .data >> equivalent), and the hack in remote.c basically makes qOffsets useless >> for most every other target that could use it. >> >> Is it simply too difficult to incorporate this patch? >> >> If we can't, I'd propose adding qSections (exactly the same syntax >> as qOffsets) that doesn't have this inflexible behaviour. > > > My vote is to include it (and possibly kill the NetWare stub at the > same time). I don't believe this stub is in use any longer. But it's > not my opinion that matters :) From memory, qOffsets has other limitations: - assumes only text, data, bss sections (which is a typical of elf) - doesn't handle delayed segment moves (why Cisco added their T reply variant which puts the segment change info in there So I wouldn't just clone the existing packet. Nothing stopping you trying to eliminate NLS. See: http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC133 for the process. Andrew