public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "abdulrahman.mahmoud75 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29921] New: GDB steps into printf() when including "cstdio" Date: Tue, 20 Dec 2022 10:39:44 +0000 [thread overview] Message-ID: <bug-29921-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29921 Bug ID: 29921 Summary: GDB steps into printf() when including "cstdio" Product: gdb Version: 7.10 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: abdulrahman.mahmoud75 at gmail dot com Target Milestone: --- I have noticed that gdb is now able to step into printf function when including cstdio starting gdb-7.10. Here is my small app: #include <cstdio> int main() { printf("test\n"); return 0; } when using GDB-7.10 to step in printf the normal behavior that it should stop at the return line but instead it stops inside the printf function: "printf (__format=0x409050 "test\n") at e:/win64-assert/modeltech/gcc-7.4.0-mingw64vc16/x86_64-w64-mingw32/include/stdio.h:351 351 __builtin_va_list __local_argv; __builtin_va_start( __local_argv, __format );" This behavior happens only on Windows. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-20 10:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-20 10:39 abdulrahman.mahmoud75 at gmail dot com [this message] 2022-12-20 13:55 ` [Bug gdb/29921] " tromey at sourceware dot org 2022-12-21 12:01 ` abdulrahman.mahmoud75 at gmail dot com
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-29921-4717@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).