public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* Re: Relocation question
@ 2005-08-11 13:51 Ton van Overbeek
  2005-08-15  4:00 ` Missing "angeldll.h" in gdb/rdi-shareestion Dave Murphy
  0 siblings, 1 reply; 3+ messages in thread
From: Ton van Overbeek @ 2005-08-11 13:51 UTC (permalink / raw)
  To: Stefan Burström, Andreas Schwab; +Cc: gdb

Andreas Schwab wrote:

>Stefan Burström <f94sbu@efd.lth.se> writes:
>
>> Can someone explain to me how gdb is supposed to handle relocated
>> executables? I am porting gdb to AmigaOS4 which relocates its
>> executables
>> when they are loaded. However, when I run an application through gdb,
>> gdb uses the bfd functions to build its map over the file. However, the
>> bfd library always relocates everything relative to 0 (since it
>> obviously doesn't know anything else to relocate it to)
>
> That reminds me of an old port of gdb 3.6 for the AtariST (which has the
> same problem).  It used CREATE_INFERIOR_HOOK (now called
> TARGET_CREATE_INFERIOR_HOOK) to query the load address of the just
> started
> process and then patched the gdb symtabs and breakpoint addresses by the
> load offset.  But I don't think that would still work nowadays.

Have a look at how we solved this in prc-tools for PalmOS:
http://prc-tools.sourceforge.net. Go to the cvs and look at the patch for
gdb. It is for gdb 5.3, but the mechanism still works for 6.x.
PalmOS can also have multiple code sections whose start addresses are not
known untill runtime. A patch supporting that is on
http://www.v-overbeek.nl/msectgdb.

Basically when execution starts (either on a real PalmOS device or on an
emulator) the start addresses of the .text and .data and other code
sections are reported to gdb, which then relocates the symbol tables.
(PalmOS is also m68k).

Hope this helps.

Ton van Overbeek
(for Andreas: my first Linux experience was with Linux-68k on Atari-TT)
(for Stefan: gjorde mitt examensarbete på LTH, Reglerteknik)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Missing "angeldll.h" in gdb/rdi-shareestion
  2005-08-11 13:51 Relocation question Ton van Overbeek
@ 2005-08-15  4:00 ` Dave Murphy
  2005-08-15  4:08   ` Daniel Jacobowitz
  0 siblings, 1 reply; 3+ messages in thread
From: Dave Murphy @ 2005-08-15  4:00 UTC (permalink / raw)
  To: gdb

Hi

While trying to build gdb-6.3 for `arm-elf` target and Mingw32 host, I get an error about a missing "angeldll.h" header. I asked about this on the Insight list some time ago but was redirected here. Where can this file be found?


thanks,
Dave

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Missing "angeldll.h" in gdb/rdi-shareestion
  2005-08-15  4:00 ` Missing "angeldll.h" in gdb/rdi-shareestion Dave Murphy
@ 2005-08-15  4:08   ` Daniel Jacobowitz
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2005-08-15  4:08 UTC (permalink / raw)
  To: Dave Murphy; +Cc: gdb

On Mon, Aug 15, 2005 at 05:00:46AM +0100, Dave Murphy wrote:
> Hi
> 
> While trying to build gdb-6.3 for `arm-elf` target and Mingw32 host, I get 
> an error about a missing "angeldll.h" header. I asked about this on the 
> Insight list some time ago but was redirected here. Where can this file be 
> found?

The rdi-share directory can't be built on Windows.

Also, gdb 6.3 doesn't support mingw32 host; so good luck... the best I
can offer right now is CodeSourcery's 2005-Q1 release or the
corresponding branch in the CVS repository.  You can find the packages
on the CodeSourcery website, and Mark's been working on getting this
support merged into the FSF tree, slowly.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-08-15  4:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-08-11 13:51 Relocation question Ton van Overbeek
2005-08-15  4:00 ` Missing "angeldll.h" in gdb/rdi-shareestion Dave Murphy
2005-08-15  4:08   ` Daniel Jacobowitz

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).