Need help in understanding gdb messages

[O.R.Senthil Kumaran]

Hi list:

Following is a piece of code:

main(int argc, char** argv)
{
int rc, result;
struct passwd *uidpwent;

/* init resources */
rpl_message_init();

/* TODO: consider placing this near webasset.c */
/* set the contributer to the name of the process owner */
uidpwent = getpwuid(getuid());
local_user = (rpl_str_t)rpl_me_malloc(strlen(uidpwent->pw_name)
+ 1); sprintf(local_user, uidpwent->pw_name);
..
..
The Question I have is w.r.t to the gdb execution o/p below:

when running gdb, with stepi what these ?? (); what does it signify and
why an instruction like 0x001469e0 in _dl_runtime_resolve () from
/lib/ld-linux.so.2(gdb) is called a number of times at different
addresses.

Please help me in understanding this.
Senthil



0x0804bef4 in rpl_message_init () at messages.c:127
127 msg_global.tptr = NULL;
(gdb)
main (argc=1, argv=0xfee29394) at rapple.c:216
216 uidpwent = getpwuid(getuid());
(gdb)
0x08049af2 216 uidpwent = getpwuid(getuid());
(gdb)
0x08049768 in ?? ()
(gdb)
0x0804976e in ?? ()
(gdb)
0x08049773 in ?? ()
(gdb)
0x080493b8 in ?? ()
(gdb)
0x080493be in ?? ()
(gdb)
0x001469e0 in _dl_runtime_resolve () from /lib/ld-linux.so.2
(gdb)
0x001469e1 in _dl_runtime_resolve () from /lib/ld-linux.so.2
(gdb)
0x001469e2 in _dl_runtime_resolve () from /lib/ld-linux.so.2
(gdb)
0x001469e3 in _dl_runtime_resolve () from /lib/ld-linux.so.2
(gdb)
0x001469e7 in _dl_runtime_resolve () from /lib/ld-linux.so.2
(gdb)
0x001469eb in _dl_runtime_resolve () from /lib/ld-linux.so.2
(gdb)
0x00146a20 in fixup () from /lib/ld-linux.so.2
(gdb)
0x00146a21 in fixup () from /lib/ld-linux.so.2
(gdb)

 

[Ravi Uday]

I think
- your executable has not been built
with GDB symbols (gcc with '-g' option) ! or
- you have attached your gdb to a process which
doesnt define that symbol or
- using wrong gdb (its specific to platform)

- Ravi

 

[Ravi Uday]

oops ! sorry that was OT !

I think
- your executable has not been built
with GDB symbols (gcc with '-g' option) ! or
- you have attached your gdb to a process which
doesnt define that symbol or
- using wrong gdb (its specific to platform)

- Ravi