public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/15360] can't step into function Date: Fri, 12 Apr 2013 08:52:00 -0000 [thread overview] Message-ID: <bug-15360-4717-4vnY71m8OY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15360-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15360 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves <palves at redhat dot com> 2013-04-12 08:52:17 UTC --- A simpler reproducer: (gdb) b function Breakpoint 1 at 0x400569: file pr15360.c, line 9. (gdb) r ... ...exited normally. GDB wants to put the breakpoint after the prologue of 'function', but: (gdb) disassemble /m function Dump of assembler code for function function(): 8 { 0x000000000040055c <+0>: push %rbp 0x000000000040055d <+1>: mov %rsp,%rbp 0x0000000000400560 <+4>: push %r12 0x0000000000400562 <+6>: push %rbx 0x0000000000400563 <+7>: sub $0x10,%rsp 0x0000000000400567 <+11>: jmp 0x40056a <function()+14> 9 do{ 0x0000000000400569 <+13>: nop 10 int i = 0; 0x000000000040056a <+14>: movl $0x0,-0x14(%rbp) -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-04-12 8:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-11 23:49 [Bug breakpoints/15360] New: " dje at google dot com 2013-04-11 23:56 ` [Bug breakpoints/15360] " dje at google dot com 2013-04-12 8:52 ` palves at redhat dot com [this message] 2013-04-12 17:59 ` tromey at redhat dot com 2013-04-12 18:16 ` palves at redhat dot com 2013-04-12 18:26 ` palves at redhat dot com 2024-01-08 16:49 ` ssbssa at sourceware dot 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-15360-4717-4vnY71m8OY@http.sourceware.org/bugzilla/ \ --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: linkBe 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).