Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Markus Teich <markus.teich@stusta.mhn.de>
To: gdb@sourceware.org
Subject: Re: Completion on static functions
Date: Fri, 12 Apr 2013 08:20:00 -0000	[thread overview]
Message-ID: <5167C3E2.9070305@stusta.mhn.de> (raw)
In-Reply-To: <83hajc9ng9.fsf@gnu.org>

Try compiling with -O0 to see if these functions indeed get inlined.

--Markus


Am 12.04.2013 10:12, schrieb Eli Zaretskii:
>> Date: Fri, 12 Apr 2013 08:47:49 +0200
>> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>> Cc: gdb@sourceware.org
>>
>> On Fri, 12 Apr 2013 08:19:22 +0200, Eli Zaretskii wrote:
>>> So does this silence mean that no one else bumped into this yet?
>>
>> there is no reproducer above.
> 
> Sorry about that.  I didn't imagine the problem was so rare.  My bad.
> 
> Try this: build the latest sharutils 4.13.4 with CFLAGS='-g3 -O2',
> then do this:
> 
>   $ cd src && gdb ./shar
>   (gdb) break generate_full_ TAB
> 
> (There is a static function named generate_full_header in shar.c.)
> 
> As mentioned before, the problem happened to me with GCC 4.7.2 on
> MinGW.  As expected, GDB reports (in "info source") that the debug
> info is DWARF 2 with preprocessor macro info.
> 
> Let me know if you need more info from GDB, I have the build directory
> handy with the object and executable files that trigger this problem.
> 


  reply	other threads:[~2013-04-12  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 16:29 Eli Zaretskii
2013-04-07 16:50 ` Eli Zaretskii
     [not found] ` <83li8o9sph.fsf@gnu.org>
2013-04-12  6:47   ` Jan Kratochvil
2013-04-12  7:01     ` Markus Teich
2013-04-12  8:13     ` Eli Zaretskii
2013-04-12  8:20       ` Markus Teich [this message]
2013-04-12  9:29         ` 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=5167C3E2.9070305@stusta.mhn.de \
    --to=markus.teich@stusta.mhn.de \
    --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