public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "elpasotileinstallation at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/26974] Wrong Value.format_string docu for static members argument
Date: Thu, 28 Oct 2021 09:11:18 +0000 [thread overview]
Message-ID: <bug-26974-4717-PISy0nFHU0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26974-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26974
Jamie <elpasotileinstallation at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |elpasotileinstallation@gmai
| |l.com
--- Comment #25 from Jamie <elpasotileinstallation at gmail dot com> ---
This bug affects the "native ARC gdb" badly and causes kernel code to jump
to addresses after the breakpoint and not executing the "breakpoint"ed
instructions at all. That "native ARC gdb" feature is not upstream yet and
is in review at the time of writing [1].
https://www.las-vegas-pool-cleaning.com/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-28 9:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 18:06 [Bug python/26974] New: " ssbssa at sourceware dot org
2020-11-29 18:09 ` [Bug python/26974] " cvs-commit at gcc dot gnu.org
2020-11-29 18:13 ` cvs-commit at gcc dot gnu.org
2020-11-29 18:14 ` ssbssa at sourceware dot org
2021-06-27 17:50 ` ahmedsayeed1982 at yahoo dot com
2021-07-15 3:08 ` sherrixotyv29 at gmail dot com
2021-08-02 5:50 ` sherrixotyv29 at gmail dot com
2021-09-02 11:05 ` donipah907 at mtlcz dot com
2021-09-02 11:15 ` mark at klomp dot org
2021-09-05 7:34 ` kimolsun2020 at yahoo dot com
2021-09-06 9:08 ` focixujo at livinginsurance dot co.uk
2021-09-06 9:12 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:37 ` mehmetgelisin at aol dot com
2021-10-04 7:57 ` olivernicholle9052 at gmail dot com
2021-10-08 14:56 ` handymanah3 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-09 17:00 ` studiaviktor at gmail dot com
2021-10-13 8:01 ` soulmate1999ethiopian at gmail dot com
2021-10-14 16:05 ` siouxfallstreeremoval at gmail dot com
2021-10-16 20:04 ` ahdeckbuilders at gmail dot com
2021-10-17 14:24 ` ahbasementremodel at gmail dot com
2021-10-19 5:31 ` pagekeller184 at gmail dot com
2021-10-19 7:14 ` progonsaytu at gmail dot com
2021-10-22 7:40 ` powerless277palms at gmail dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-10-27 6:40 ` bathroomremodelrr at gmail dot com
2021-10-28 9:11 ` elpasotileinstallation at gmail dot com [this message]
2021-11-03 7:51 ` barronwbs85 at gmail dot com
2021-11-13 19:34 ` tesaso8237 at funboxcn dot com
2021-11-18 9:55 ` cheesecakesuperhuman at gmail dot com
2021-11-22 6:48 ` gexed96894 at keagenan dot com
2021-11-25 6:04 ` thebestdressedog 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-26974-4717-PISy0nFHU0@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: link
Be 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).