This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: relocating BSS section for remote target
- From: "Liang, James" <jliang at sandia dot gov>
- To: "'gdb at sources dot redhat dot com'" <gdb at sources dot redhat dot com>
- Date: Mon, 21 Apr 2003 16:20:09 -0600
- Subject: RE: relocating BSS section for remote target
Never mind, I figured it out. I had removed the BSS section from my image
to save ROM space. This allowed the debug symbols for the BSS section to
stay, but changed something in the image that made GDB (symfile.c to be
exact) think that I had no BSS section. That's why the relocation did
happen.
I fixed it by having my code look for the BSS section when it is not tagged
and updating the GDB data structure.
-----Original Message-----
From: Liang, James
Sent: Monday, April 21, 2003 1:48 PM
To: 'gdb at sources dot redhat dot com'
Subject: relocating BSS section for remote target
I am trying to understand how the code for remote targets works for GDB.
In remote_cisco_objfile_relocate of remote.c, it looks like the data, text,
and bss sections are all relocated.
The problem is that when I try to access something in my bss section, it
still tries to access it at the
old unrelocated address. What could be causing this?
James