public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Fei Ding <fdingiit@gmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Fwd: Problem about getopt.c
Date: Fri, 20 Mar 2015 08:20:00 -0000	[thread overview]
Message-ID: <CAGmPkf+w8xzyRMHEP8Jx1CqB2A_ss4rX_Qfs=h7ZtW74RYhtMA@mail.gmail.com> (raw)
In-Reply-To: <CAGmPkfJow2J2J_80Dk4FHwVX4-mYCgPVzsAiPeb2VHDnGENaFQ@mail.gmail.com>

And I am using gdb to debug gdb. You can get getopt.c in gdb/libiberty/getopt.c

---------- Forwarded message ----------
From: Fei Ding <fdingiit@gmail.com>
Date: 2015-03-20 16:05 GMT+08:00
Subject: Problem about getopt.c
To: "gdb@sourceware.org" <gdb@sourceware.org>


I've send a mail talking about problem about getopt.c, and I will
describe it a litter clear here.

I want to trace source code of _getopt_internal() in getopt.c, so I
try to make a breakpoint on _getopt_internal, but gdb tell me there is
no such symbol and breakpoint set failed, so, I try to set breakpoint
as filename:linenum, but I cannot get getopt.c, gdb tell me no such
file. I set the directiory, no effect. And then, I use nm tool of UNIX
to check libiberty.a, which getopt.o will be merged into. And I get
this:

/////////////////////////////////////////
getopt.o:

getopt1.o:

getpwd.o:
                 U __errno_location
0000000000000008 b failure_errno.3486
                 U free
                 U getcwd
                 U getenv
0000000000000000 T getpwd
0000000000000000 b pwd.3485
                 U stat
                 U xmalloc
/////////////////////////////////////////

Nothing there in getopt.o and getopt1.o, it is so strange to me.
What's more, I write a printf() in the beginning of
_getopt_internal(), and make clean && make && make install, but there
is no printing message.

Did I miss something?

  reply	other threads:[~2015-03-20  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  8:05 Fei Ding
2015-03-20  8:20 ` Fei Ding [this message]
2015-03-20 10:54 ` Eli Zaretskii

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='CAGmPkf+w8xzyRMHEP8Jx1CqB2A_ss4rX_Qfs=h7ZtW74RYhtMA@mail.gmail.com' \
    --to=fdingiit@gmail.com \
    --cc=gdb@sourceware.org \
    /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).