public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yangyibiao at hust dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/95432] New: inconsistent behaviors at -O2
Date: Sat, 30 May 2020 03:02:03 +0000	[thread overview]
Message-ID: <bug-95432-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95432

            Bug ID: 95432
           Summary: inconsistent behaviors at -O2
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: yangyibiao at hust dot edu.cn
  Target Milestone: ---

Consider test case:
...
$ cat small.c
__attribute__ ((noinline, noclone)) 
int foo (char *c)
{
  asm volatile ("" : : "r" (c) : "memory");
  return 1;
}

int main ()
{
  char tpl1[20] = "/tmp/test.XXX";
  char tpl2[20] = "/tmp/test.XXX";
  int fd1 = foo (tpl1);
  int fd2 = foo (tpl2);
  if (fd1 == -1) {
    return 1;
  }

  return 0;
}
...



When stepping with step, line 13 is not hit by gdb.
...
$ gcc -O2 -g small.c; gdb -q a.out
Reading symbols from a.out...
(gdb) b main
Breakpoint 1 at 0x401020: file small.c, line 10.
(gdb) r
Starting program: /home/yibiao/Debugger/a.out 

Breakpoint 1, main () at small.c:10
10        char tpl1[20] = "/tmp/test.XXX";
(gdb) step
11        char tpl2[20] = "/tmp/test.XXX";
(gdb) 
12        int fd1 = foo (tpl1);
(gdb) 
foo (c=c@entry=0x7fffffffdea0 "/tmp/test.XXX") at small.c:5
5         return 1;
(gdb) 
foo (c=c@entry=0x7fffffffdec0 "/tmp/test.XXX") at small.c:5
5         return 1;
(gdb) 
main () at small.c:14
14        if (fd1 == -1) {
(gdb) 
0x00007ffff7df4023 in __libc_start_main () from /usr/lib/libc.so.6
(gdb) 
Single stepping until exit from function __libc_start_main,
which has no line number information.
[Inferior 1 (process 1852557) exited normally]
...



When stepping with stepi, line 13 is hit by gdb as follow.
...
$ gcc -O2 -g small.c; gdb -q a.out
Reading symbols from a.out...
(gdb) b main
Breakpoint 1 at 0x401020: file small.c, line 10.
(gdb) r
Starting program: /home/yibiao/Debugger/a.out 

Breakpoint 1, main () at small.c:10
10        char tpl1[20] = "/tmp/test.XXX";
(gdb) stepi
0x0000000000401024      10        char tpl1[20] = "/tmp/test.XXX";
(gdb) 
0x000000000040102c      12        int fd1 = foo (tpl1);
(gdb) 
0x000000000040102f      10        char tpl1[20] = "/tmp/test.XXX";
(gdb) 
11        char tpl2[20] = "/tmp/test.XXX";
(gdb) 
12        int fd1 = foo (tpl1);
(gdb) 
0x0000000000401043      11        char tpl2[20] = "/tmp/test.XXX";
(gdb) 
0x0000000000401048      12        int fd1 = foo (tpl1);
(gdb) 
foo (c=c@entry=0x7fffffffdea0 "/tmp/test.XXX") at small.c:5
5         return 1;
(gdb) 
0x0000000000401165      5         return 1;
(gdb) 
0x000000000040104d in main () at small.c:13
13        int fd2 = foo (tpl2);
(gdb) 
...


$ gcc --version
gcc (GCC) 10.0.1 20200419 (experimental)
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ gdb --version
GNU gdb (GDB) 10.0.50.20200517-git
Copyright (C) 2020 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.

             reply	other threads:[~2020-05-30  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30  3:02 yangyibiao at hust dot edu.cn [this message]
2020-05-30  3:03 ` [Bug debug/95432] " yangyibiao at hust dot edu.cn
2021-03-07  7:25 ` pinskia at gcc dot gnu.org
2021-03-07 14:42 ` vries at gcc dot gnu.org
2021-03-07 20:27 ` pinskia at gcc dot gnu.org

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=bug-95432-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).