From: Daniel Jacobowitz <drow@mvista.com>
To: Raja Saleru <iap_sraja@access.co.jp>
Cc: saleru raja <saleru_raja@email.com>, gdb@sources.redhat.com
Subject: Re: qSymbol
Date: Tue, 17 Jun 2003 02:18:00 -0000 [thread overview]
Message-ID: <20030617021756.GA22254@nevyn.them.org> (raw)
In-Reply-To: <OHEKKPPLCJNKIDELCLGOAEBBCBAA.iap_sraja@access.co.jp>
On Mon, Jun 17, 2002 at 11:08:21AM +0900, Raja Saleru wrote:
For the fourth time, please fix the year on your computer if you wish
to continue this conversation. Having your mail sort to the stop is
very annoying.
> Hello Sir, the following is the function definition,
>
> static void
> linux_look_up_symbols (void)
> {
> #ifdef USE_THREAD_DB
> if (using_threads)
> return;
>
> using_threads = thread_db_init ();
> #endif
> }
>
> assume that I am interested in only process debugging, but not thread
> debugging,
> so I am not defining USE_THREAD_DB macro.
>
> I am getting confuse... why target sending symbols to host (gdb ) ?
>
> If I compile the application at host side as re-locatable and relink it at
> target side, the sybols are there at host side only.
> the corresponding values at target side. This is what I thought.. what will
> be solution in this case ?
> can you carrify me more in details ?
qSymbol is a mechanism _for the target_ to ask the _host_ about the
address of a symbol. You appear to have the opposite problem, so you
will need something different.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-17 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 4:17 qSymbol saleru raja
2003-06-16 12:50 ` qSymbol Daniel Jacobowitz
2003-06-17 2:08 ` qSymbol Raja Saleru
2003-06-17 2:18 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-16 2:46 qSymbol saleru raja
2003-06-16 3:23 ` qSymbol Daniel Jacobowitz
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=20030617021756.GA22254@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=iap_sraja@access.co.jp \
--cc=saleru_raja@email.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