This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Broken remote protocol qOffsets response handling


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.

Earl


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]