Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kevin \"Squail\" Endres" <kevine@wildseed.com>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: gdbserver and arm - please help
Date: Thu, 25 Apr 2002 16:04:00 -0000	[thread overview]
Message-ID: <43CB1396676FD4119F03001083FD2994F5F15D@neptune.kirkland.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

i am trying to get gdbserver working on the arm (through applying various
patches - i can get it to build correctly - but it doesnt function as i
would expect)

i386 environment: gdb-5.1.1 crosstargeted for arm binaries (i can read the
symbol info from the binaries correctly - it works as expected)

arm: gdbserver built for the arm target with the attached patches applied (i
built the full gdb targeted and hosted on the arm - it works correctly on
the arm) - i also edited config.h in the gdb dir to define the NM file
(config/arm/nm-linux.h) - it compiles without error.

when i run a program under gdbserver and target remote via gdb (using TCP) -
the connection is formed but i get:

0x40002520 in ??() echoed to gdb.

if i do 'info stack' in gdb

i get:
#0 0x40002520 in ??()
#1 0x0000000 in ??() in gdb

if i 'step' or 'next':
'Cannot find bounds of current function'

kill terminates the program as expected.

Any help is appreciated!

:]k


[-- Attachment #2: low-linux.patch --]
[-- Type: application/octet-stream, Size: 923 bytes --]

*** insight.orig/insight-5.1.1/gdb/gdbserver/low-linux.c	Wed Jul 25 22:23:58 2001
--- insight/insight-5.1.1/gdb/gdbserver/low-linux.c	Tue Apr 23 18:07:17 2002
***************
*** 24,27 ****
--- 24,28 ----
  #include "frame.h"
  #include "inferior.h"
+ #include "tm.h"
  
  #include <stdio.h>
***************
*** 263,266 ****
--- 264,289 ----
    return (blockend + 4 * regmap[regnum]);
  }
+ //JOE: Add this to enable compilation on arm
+ 
+ #elif defined(ARM_GNULINUX_TARGET)
+ static void
+ initialize_arch (void)
+ {
+   return;
+ }
+ 
+ int
+ arm_linux_register_u_addr (int blockend, int regnum)
+ {
+   return blockend + REGISTER_BYTE (regnum);
+ }
+ 
+ #if !defined (REGISTER_U_ADDR)
+ #define REGISTER_U_ADDR(addr,blockend,regno)  \
+    addr = arm_linux_register_u_addr (blockend, regno)
+ #endif
+ 
+ //END JOE ADD
+ 
  #elif defined(IA64_GNULINUX_TARGET)
  #undef NUM_FREGS

[-- Attachment #3: tm-linux.patch --]
[-- Type: application/octet-stream, Size: 543 bytes --]

*** insight.orig/insight-5.1.1/gdb/config/arm/tm-linux.h	Tue Sep  5 20:39:11 2000
--- insight/insight-5.1.1/gdb/config/arm/tm-linux.h	Tue Apr 23 18:12:07 2002
***************
*** 158,160 ****
--- 158,165 ----
  #define SIGCONTEXT_REGISTER_ADDRESS arm_linux_sigcontext_register_address
  
+ //JOE Add this as described in the patch to support arm compilation
+ /* Define to support ARM Linux in gdbserver/low-linux.c. */
+ #define ARM_GNULINUX_TARGET
+ #define U_REGS_OFFSET 0
+ #undef  HAVE_SYS_REG_H
  #endif /* TM_ARMLINUX_H */

             reply	other threads:[~2002-04-25 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 16:04 Kevin "Squail" Endres [this message]
2002-04-25 16:08 ` Daniel Jacobowitz
2002-04-25 17:23 Kevin "Squail" Endres
2002-04-25 17:31 ` Daniel Jacobowitz
2002-04-25 17:34 Kevin "Squail" Endres

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=43CB1396676FD4119F03001083FD2994F5F15D@neptune.kirkland.local \
    --to=kevine@wildseed.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