public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dushistov at mail dot ru" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/10112] do not stop on function
Date: Wed, 29 Apr 2009 11:54:00 -0000	[thread overview]
Message-ID: <20090429115450.12629.qmail@sourceware.org> (raw)
In-Reply-To: <20090429113846.10112.dushistov@mail.ru>


------- Additional Comments From dushistov at mail dot ru  2009-04-29 11:54 -------
(In reply to comment #1)
> > gcc -ggdb -Wall test.c -o test_gdb && gdb test_gdb
> 
> Most likely, the function wasn't called at all.  The
> compiler probably inlined it in main.  You can confirm
> that by looking at the disassembly of test_gdb.
> 
> Try recompiling, but this time, disabling optimizations:
>  gcc -O0 -ggdb -Wall test.c -o test_gdb && gdb test_gdb
>       ^^
> 

I don't think so, because of from documentation of gcc:
`-O0'
     Reduce compilation time and make debugging produce the expected
     results.  This is the default.

so it should be -O0 if no optimization parameters was used,
any way:

>gcc -O0 -ggdb -Wall test.c -o test_gdb && gdb test_gdb
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) br f
Breakpoint 1 at 0x80483f8: file test.c, line 6.
(gdb) r
Starting program: /var/tmp/test_gdb 
f was called

Program exited normally.
(gdb) 

the problem is place of breakpoint,
(gdb) info breakpoints
Num     Type           Disp Enb Address    What
1       breakpoint     keep y   0x080483f8 in f at test.c:6

(gdb) li f
1       #include <stdio.h>
2
3       void f(int gwk, double gsec)
4       {
5               while (gsec < 0.0) {
6                       gwk--;


so as you can see I put breakpoin of "f", but gdb put breakpoint
into while loop, and never happened, because of this example gsec >= 0



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10112

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-04-29 11:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 11:38 [Bug breakpoints/10112] New: " dushistov at mail dot ru
2009-04-29 11:48 ` [Bug breakpoints/10112] " pedro at codesourcery dot com
2009-04-29 11:49 ` pedro at codesourcery dot com
2009-04-29 11:54 ` dushistov at mail dot ru [this message]
2009-04-29 12:06 ` pedro at codesourcery dot com
2009-04-29 12:09 ` dushistov at mail dot ru
2009-10-21 18:02 ` dushistov at mail dot ru
2009-10-21 19:27 ` ppluzhnikov at google dot com
2009-10-22 17:13 ` dushistov at mail dot ru
2009-10-22 17:16 ` dushistov at mail dot ru
2009-10-22 17:47 ` ppluzhnikov at google dot com
2010-08-14  2:49 ` pedro at codesourcery dot com
     [not found] <bug-10112-4717@http.sourceware.org/bugzilla/>
2011-05-23 13:12 ` dushistov at mail dot ru

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=20090429115450.12629.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).