* relocating BSS section for remote target
@ 2003-04-21 19:47 Liang, James
0 siblings, 0 replies; 2+ messages in thread
From: Liang, James @ 2003-04-21 19:47 UTC (permalink / raw)
To: 'gdb@sources.redhat.com'
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: relocating BSS section for remote target
@ 2003-04-21 22:20 Liang, James
0 siblings, 0 replies; 2+ messages in thread
From: Liang, James @ 2003-04-21 22:20 UTC (permalink / raw)
To: 'gdb@sources.redhat.com'
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@sources.redhat.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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-04-21 22:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-21 19:47 relocating BSS section for remote target Liang, James
2003-04-21 22:20 Liang, James
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).