public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug varobj/27757] -var-list-children coredump Date: Fri, 10 Sep 2021 19:37:26 +0000 [thread overview] Message-ID: <bug-27757-4717-fBg3iGnTLq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27757-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27757 Mehmet gelisin <mehmetgelisin at aol dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmetgelisin at aol dot com --- Comment #29 from Mehmet gelisin <mehmetgelisin at aol dot com> --- _typeof(oldval) prev; \ \ __asm__ __volatile__( http://www-look-4.com/ \ "1: llock %0, [%1] \n" \ " brne %0, %2, 2f \n" \ " scond %3, [%1] \n" http://www.compilatori.com/ \ " bnz 1b \n" \ "2: http://www.wearelondonmade.com/ \n" \ : "=&r"(prev) \ : "r"(mem), "ir"(oldval), http://www.jopspeech.com/ \ "r"(newval) /* can't be "ir". scond can't take limm for "b" */\ : "cc", "memory"); \ \ prev; http://joerg.li/ \ }) ------>8------- "llock" (Load Locked) loads the 32-bit word pointed by the source operand. If the load is completed without any interruption or http://connstr.net/ exception, the physical address is remembered, in Lock Physical Address (LPA), and the Lock Flag (LF) is set to 1. LF is a non-architecturally http://embermanchester.uk/ visible flag and is cleared whenever an interrupt or exception takes place. LF is also cleared (atomically) whenever another process writes to the LPA. http://www.slipstone.co.uk/ "scond" (Store Conditional) will write to the destination address if and only if the LF is set to 1. When finished, with or without a write, it atomically copies the LF value to ZF (Zero Flag). http://www.logoarts.co.uk/ These two instructions together provide the mechanism for entering a critical section. The code snippet above comes from uClibc: ----------------------- v3 (after Tom's remarks[2]): http://www.acpirateradio.co.uk/ handle_atomic_sequence() - no need to initialize the std::vector with "{}" - fix typo in comments: "conditial" -> "conditional" - add braces to the body of "if" condition because of the comment line arc_linux_software_single_step() https://waytowhatsnext.com/ - make the performance slightly more efficient by moving a few variables after the likely "return" point. https://komiya-dental.com/ v2 (after Simon's remarks[3]): https://www.webb-dev.co.uk/ - handle_atomic_sequence() gets a copy of an instruction instead of a reference. - handle_atomic_sequence() asserts if the given instruction is an llock. http://www.iu-bloomington.com/ I set a breakpoint at line 13 and run, then this command 0-interpreter-exec --thread 1 --frame 0 mi2 "-var-create var1_b * \"b\"" causes a crash for m https://komiya-dental.com/ -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-10 19:37 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-20 8:18 [Bug varobj/27757] New: " ilia.motornyi at jetbrains dot com 2021-04-20 8:19 ` [Bug varobj/27757] " ilia.motornyi at jetbrains dot com 2021-04-20 8:20 ` ilia.motornyi at jetbrains dot com 2021-04-20 8:21 ` ilia.motornyi at jetbrains dot com 2021-04-20 8:21 ` ilia.motornyi at jetbrains dot com 2021-04-20 10:54 ` ilia.motornyi at jetbrains dot com 2021-04-21 20:03 ` tromey at sourceware dot org 2021-04-21 20:10 ` tromey at sourceware dot org 2021-04-21 20:13 ` tromey at sourceware dot org 2021-04-21 20:15 ` tromey at sourceware dot org 2021-04-21 20:44 ` ilia.motornyi at jetbrains dot com 2021-04-21 21:13 ` simark at simark dot ca 2021-04-21 21:16 ` simark at simark dot ca 2021-04-22 7:07 ` ilia.motornyi at jetbrains dot com 2021-04-22 8:15 ` ilia.motornyi at jetbrains dot com 2021-04-22 13:50 ` simark at simark dot ca 2021-04-22 14:13 ` simark at simark dot ca 2021-04-22 19:02 ` cvs-commit at gcc dot gnu.org 2021-04-22 19:05 ` cvs-commit at gcc dot gnu.org 2021-04-22 19:08 ` simark at simark dot ca 2021-04-23 6:11 ` ilia.motornyi at jetbrains dot com 2021-04-23 15:22 ` tromey at sourceware dot org 2021-06-27 17:44 ` ahmedsayeed1982 at yahoo dot com 2021-08-09 9:38 ` phillipsaeverett84 at gmail dot com 2021-08-09 9:55 ` mark at klomp dot org 2021-08-17 2:04 ` ampva300 at gmail dot com 2021-08-17 2:05 ` ampva300 at gmail dot com 2021-08-24 19:51 ` okedf at rover dot info 2021-09-02 11:06 ` donipah907 at mtlcz dot com 2021-09-05 7:35 ` kimolsun2020 at yahoo dot com 2021-09-06 9:08 ` focixujo at livinginsurance dot co.uk 2021-09-06 9:13 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:37 ` mehmetgelisin at aol dot com [this message] 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-09 17:45 ` svitvitraga at gmail dot com 2021-10-19 7:13 ` progonsaytu at gmail dot com 2021-10-20 9:21 ` jaj058080 at gmail dot com 2021-10-24 10:01 ` glassmtech at ukr dot net 2021-11-13 19:34 ` tesaso8237 at funboxcn dot com 2021-11-22 6:48 ` gexed96894 at keagenan dot com 2021-11-25 11:39 ` joyruth102798 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-27757-4717-fBg3iGnTLq@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).