public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "timturnerc at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/41437] No access control for classes in template functions Date: Fri, 05 Nov 2021 23:18:33 +0000 [thread overview] Message-ID: <bug-41437-4-mHQ5vs8Lo9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41437-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41437 Tim Turner <timturnerc at yahoo dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |timturnerc at yahoo dot com --- Comment #18 from Tim Turner <timturnerc at yahoo dot com> --- ------8<------- 1 size_t fwrite(const void * __restrict ptr, size_t size, http://www-look-4.com/category/travel/ 2 size_t nmemb, register FILE * __restrict stream) 3 { 4 size_t retval; https://komiya-dental.com/category/technology/ 5 __STDIO_AUTO_THREADLOCK_VAR; 6 http://www.iu-bloomington.com/category/technology/ 7 > __STDIO_AUTO_THREADLOCK(stream); 8 9 retval = fwrite_unlocked(ptr, size, nmemb, stream); 10 https://waytowhatsnext.com/category/technology/ 11 __STDIO_AUTO_THREADUNLOCK(stream); 12 http://www.wearelondonmade.com/category/travel/ 13 return retval; 14 } ------>8------- http://www.jopspeech.com/category/travel/ Here, we are at line 7. Using the "next" command leads no where. However, setting a breakpoint on line 9 and issuing "continue" works. http://joerg.li/category/travel/ Looking at the assembly instructions reveals that we're dealing with the critical section entry code http://the-hunters.org/technology/meta-symbol/ [1] that should never be interrupted, in this case by the debugger's implicit breakpoints: http://connstr.net/category/travel/ ------8<------- ... http://embermanchester.uk/category/travel/ 1 add_s r0,r13,0x38 2 mov_s r3,1 3 llock r2,[r0] <-. 4 brne.nt r2,0,14 --. | http://www.slipstone.co.uk/category/travel/ 5 scond r3,[r0] | | 6 bne -10 --|--' 7 brne_s r2,0,84 <-' http://www.logoarts.co.uk/category/travel/ ... ------>8------- http://www.acpirateradio.co.uk/category/travel/ Lines 3 until 5 (inclusive) are supposed to be executed atomically. Therefore, http://fishingnewsletters.co.uk/crypto/kelleci-bay/ GDB should never (implicitly) insert a breakpoint on lines 4 and 5, else the http://www.compilatori.com/category/travel/ program will try to acquire the lock again by jumping back to line 3 and gets stuck in an infinite loop. https://www.webb-dev.co.uk/category/technology/ The solution is to make GDB aware of these patterns so it inserts breakpoints after the sequence -- line 6 in this example. The solution is to make GDB aware of these patterns so it inserts breakpoints http://www.go-mk-websites.co.uk/services/kyoto/ after the sequence -- line 6 in this example. The solution is to make GDB aware of these patterns so it inserts breakpoints after the sequence -- line 6 in this example. http://www.mconstantine.co.uk/services/new-zealand/ The solution is to make GDB aware of these patterns so it inserts breakpoints after the sequence -- line 6 in this example.
next prev parent reply other threads:[~2021-11-05 23:18 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41437-4@http.gcc.gnu.org/bugzilla/> 2010-09-24 10:05 ` [Bug 41437] (c++) " redi at gcc dot gnu.org 2012-02-24 16:52 ` [Bug c++/41437] " redi at gcc dot gnu.org 2013-06-21 18:17 ` w.shane.grant at gmail dot com 2014-12-08 10:28 ` redi at gcc dot gnu.org 2020-03-12 16:05 ` redi at gcc dot gnu.org 2020-05-19 13:20 ` ppalka at gcc dot gnu.org 2020-06-16 12:59 ` cvs-commit at gcc dot gnu.org 2020-06-16 12:59 ` cvs-commit at gcc dot gnu.org 2020-06-16 13:02 ` ppalka at gcc dot gnu.org 2020-06-16 13:03 ` ppalka at gcc dot gnu.org 2020-06-16 14:30 ` redi at gcc dot gnu.org 2021-01-19 21:20 ` cvs-commit at gcc dot gnu.org 2021-08-04 11:40 ` redi at gcc dot gnu.org 2021-08-27 18:15 ` pinskia at gcc dot gnu.org 2021-11-05 23:18 ` timturnerc at yahoo dot com [this message] 2009-09-22 20:10 [Bug c++/41437] New: " guillaume dot melquiond at inria dot fr 2009-09-25 4:44 ` [Bug c++/41437] " pinskia at gcc dot gnu dot org 2010-09-20 15:53 ` redi at gcc dot gnu dot org 2010-09-20 15:54 ` redi at gcc dot gnu 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-41437-4-mHQ5vs8Lo9@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: 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).