Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@iskramedical.si>
To: gdb@sources.redhat.com
Subject: remote debugging and source files
Date: Tue, 24 Aug 2004 14:05:00 -0000	[thread overview]
Message-ID: <412B4B05.8060705@iskramedical.si> (raw)

Hi,

I'm remote debugging a programm using gdbserver on target side and gdb 
on host side. My target CPU is ARM and host is i686. Debugging same 
program just on host (no cross compilaton) allows me to see the source 
of each file when doing 'step'. That does not work when same program is 
cross-compiled, copied to target and started there with:
	gdbserver host:2345 slider

On host I run the debugger- 'ddd --debugger arm-linu-gdb', load the 
program and specify the target:
	target remote ipaq:2345

I can see slider.c source displayed, but any other functions, defined 
outside, are not stepped into. Maybe it is worth mentioning that this 
functions are in a shared library.

I tried adding directory of the actual source with 'dir /path/to/source' 
but it didn't help.

Also, I pointed 'set solib-search-path' to libs containing those functions.

What am I missing here?

regards,
h

-- 
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"Aì rén"	|	[Analects XII:22]


             reply	other threads:[~2004-08-24 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:05 Hinko Kocevar [this message]
2004-08-24 15:34 ` Hinko Kocevar
2004-08-24 15:56   ` Hinko Kocevar
2004-08-24 16:35     ` Kris Warkentin
2004-08-24 17:42       ` Hinko Kocevar
2004-08-24 17:53         ` Daniel Jacobowitz
2004-08-24 18:05         ` Kris Warkentin
2004-08-25 13:58           ` Hinko Kocevar
2004-08-25 14:16             ` Daniel Jacobowitz
2004-08-25 14:30               ` Hinko Kocevar
2004-08-26 19:38                 ` remote debugging and source files - SOLVED Hinko Kocevar
2004-08-25 14:33             ` remote debugging and source files Kris Warkentin

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=412B4B05.8060705@iskramedical.si \
    --to=hinko.kocevar@iskramedical.si \
    --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