From: "Raja Saleru" <iap_sraja@access.co.jp>
To: "Gdb Redhat" <gdb@sources.redhat.com>
Subject: gdbserver Linux_low.c
Date: Mon, 09 Jun 2003 09:55:00 -0000 [thread overview]
Message-ID: <OHEKKPPLCJNKIDELCLGOMENPCAAA.iap_sraja@access.co.jp> (raw)
Hi
In gdbserver source file Linux_low.c look at the following data structure
static struct target_ops linux_target_ops = {
linux_create_inferior,
linux_attach,
linux_kill,
linux_thread_alive,
linux_resume,
linux_wait,
linux_fetch_registers,
linux_store_registers,
linux_read_memory,
linux_write_memory,
linux_look_up_symbols,
};
the last member linux_look_up_symbols, what this function does ?
This is assigned to the following function
linux_look_up_symbols (void)
{
#ifdef USE_THREAD_DB
if (using_threads)
return;
using_threads = thread_db_init ();
#endif
}
Actually where it does any symbol related functionality ?
can anybody clarrify these questions ? Thanks in advance
Regards
Raja Saleru
next reply other threads:[~2003-06-09 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 9:55 Raja Saleru [this message]
2003-06-09 13:21 ` Daniel Jacobowitz
[not found] ` <3D040614.000001.01632@ADMIN.access.co.jp>
2003-06-10 4:39 ` 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=OHEKKPPLCJNKIDELCLGOMENPCAAA.iap_sraja@access.co.jp \
--to=iap_sraja@access.co.jp \
--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