public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13262] New: Hide artificial inlines (at least by default) Date: Wed, 05 Oct 2011 16:40:00 -0000 [thread overview] Message-ID: <bug-13262-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13262 Bug #: 13262 Summary: Hide artificial inlines (at least by default) Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: jakub@redhat.com Classification: Unclassified As discussed in http://gcc.gnu.org/ml/gcc-patches/2011-10/msg00348.html and for further info see http://gcc.gnu.org/ml/gcc-patches/2007-08/msg02300.html and following thread, it doesn't seem GDB hides by default artificial inline functions. glibc and gcc *intrin*.h headers use the artificial attribute extensively where those inlines shouldn't be visible to the user during single stepping and backtrace. extern __inline __attribute__ ((__always_inline__,__artificial__,__gnu_inline__)) char * __attribute__ ((__nothrow__)) strcpy (char *__restrict __dest, __const char *__restrict __src) { return __builtin___strcpy_chk (__dest, __src, __builtin_object_size (__dest, 2 > 1)); } char buf[6]; int main(int argc, char **argv) { strcpy (buf,"hello "); asm volatile ("" : : : "memory"); return 0; } IMHO the hiding should be just the default behavior, with a way to enable seeing them in backtraces and seeing them on step through. -- 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 reply other threads:[~2011-10-05 16:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-05 16:40 jakub at redhat dot com [this message] 2024-01-09 19:46 ` [Bug gdb/13262] " 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-13262-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).