public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@iskramedical.si>
To: gdb@sources.redhat.com
Cc: Daniel Jacobowitz <drow@false.org>, Kris Warkentin <kewarken@qnx.com>
Subject: Re: remote debugging and source files - SOLVED
Date: Thu, 26 Aug 2004 19:38:00 -0000	[thread overview]
Message-ID: <412E3C12.5010502@iskramedical.si> (raw)
In-Reply-To: <412CA271.2020302@iskramedical.si>

Hinko Kocevar wrote:

> 
> This would certainly be the case then, I'll update that board and repost...
> 

As you guys pointed out, it helps having same libs and binaries on both 
target and host side of debugging enviroment.

Thanks for sharing your wisdom.

But, now that symbols get loaded automagically on shared library event, 
other set and enabled breakpoints in debugged program don't stop 
execution?! I already post another topic about this.

Now I'm more confident in what is the reason - its probably libraries 
itself, since debugging worked just fine (except for the symbol loading) 
with the old ones.

Is there any special case with building libraries to be used process of 
debugging?

-- 
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-26 19:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:05 remote debugging and source files Hinko Kocevar
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                 ` Hinko Kocevar [this message]
2004-08-25 14:33             ` 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=412E3C12.5010502@iskramedical.si \
    --to=hinko.kocevar@iskramedical.si \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=kewarken@qnx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).