From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Broken remote protocol qOffsets response handling
Date: Thu, 12 Sep 2002 08:40:00 -0000 [thread overview]
Message-ID: <3D80B56B.6090601@ges.redhat.com> (raw)
In-Reply-To: <20020912145801.GA3404@nevyn.them.org>
> 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
next prev parent reply other threads:[~2002-09-12 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 7:13 Earl Chew
2002-09-12 7:57 ` Daniel Jacobowitz
2002-09-12 8:40 ` Andrew Cagney [this message]
2002-09-12 11:06 ` Andrew Cagney
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=3D80B56B.6090601@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb@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