public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gulsenenginar at aol dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/27194] put rust demangler on 10.x branch
Date: Sat, 09 Oct 2021 11:00:29 +0000 [thread overview]
Message-ID: <bug-27194-4717-n2Yecwzwfr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27194-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27194
Gulsen Engin <gulsenenginar at aol dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gulsenenginar at aol dot com
--- Comment #26 from Gulsen Engin <gulsenenginar at aol dot com> ---
Tentative patch:
...
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
https://www.webb-dev.co.uk/computers/crypto-apps/
index f318a125319..c20c0d7d649 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c http://www.compilatori.com/health/premium-subscription/
@@ -3625,11 +3625,10 @@ create_exception_master_breakpoint (void)
if (create_exception_master_breakpoint_probe (obj))
continue;
http://www.acpirateradio.co.uk/health/transportation-security/
- /* Iterate over separate debug objects and try an _Unwind_DebugHook
- kind breakpoint. */
http://www.logoarts.co.uk/health/printers-for-health/
- for (objfile *sepdebug = obj->separate_debug_objfile;
- sepdebug != nullptr; sepdebug = sepdebug->separate_debug_objfile)
- if (create_exception_master_breakpoint_hook (sepdebug))
http://www.slipstone.co.uk/health/sound-systems/
+ /* Iterate over main and separate debug objects and try an
+ _Unwind_DebugHook kind breakpoint. */
+ for (objfile *debug_objfile : obj->separate_debug_objfiles ())
http://embermanchester.uk/health/social-privacy/
+ if (create_exception_master_breakpoint_hook (debug_objfile))
break;
Tentative patch: http://connstr.net/health/usb-chargers/
...
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index f318a125319..c20c0d7d649 100644 http://joerg.li/property/latest-suvs/
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -3625,11 +3625,10 @@ create_exception_master_breakpoint (void)
http://www.jopspeech.com/property/slim-pen-2/
if (create_exception_master_breakpoint_probe (obj))
continue; http://www.wearelondonmade.com/health/check-ups/
- /* Iterate over separate debug objects and try an _Unwind_DebugHook
- kind breakpoint. */
- for (objfile *sepdebug = obj->separate_debug_objfile;
https://waytowhatsnext.com/computers/discord-and-steam/
- sepdebug != nullptr; sepdebug = sepdebug->separate_debug_objfile)
- if (create_exception_master_breakpoint_hook (sepdebug))
http://www.iu-bloomington.com/computers/real-me-gt2/
+ /* Iterate over main and separate debug objects and try an
+ _Unwind_DebugHook kind breakpoint. */
https://komiya-dental.com/computers/huawei-technology/
+ for (objfile *debug_objfile : obj->separate_debug_objfiles ())
+ if (create_exception_master_breakpoint_hook (debug_objfile))
break; http://www-look-4.com/health/winter-sickness/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-09 11:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 17:07 [Bug rust/27194] New: " tromey at sourceware dot org
2021-01-16 17:07 ` [Bug rust/27194] " tromey at sourceware dot org
2021-01-16 17:27 ` tromey at sourceware dot org
2021-06-27 17:51 ` ahmedsayeed1982 at yahoo dot com
2021-07-15 1:39 ` sherrixotyv29 at gmail dot com
2021-07-25 4:02 ` ampva300 at gmail dot com
2021-07-27 6:29 ` sherrixotyv29 at gmail dot com
2021-08-07 1:46 ` towingwpg at gmail dot com
2021-08-08 1:44 ` towingwpg at gmail dot com
2021-08-15 5:47 ` damienaloysius at gmail dot com
2021-08-18 13:52 ` jamesrogan59 at gmail dot com
2021-09-02 11:05 ` donipah907 at mtlcz dot com
2021-09-02 11:09 ` mark at klomp dot org
2021-09-05 7:34 ` kimolsun2020 at yahoo dot com
2021-09-06 9:06 ` focixujo at livinginsurance dot co.uk
2021-09-06 9:12 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:38 ` mehmetgelisin at aol dot com
2021-09-26 2:42 ` spanksaucee01 at gmail dot com
2021-09-26 2:53 ` spanksaucee01 at gmail dot com
2021-09-26 2:59 ` spanksaucee01 at gmail dot com
2021-09-26 3:11 ` spanksaucee01 at gmail dot com
2021-09-26 3:17 ` spanksaucee01 at gmail dot com
2021-09-26 3:22 ` spanksaucee01 at gmail dot com
2021-09-26 3:28 ` spanksaucee01 at gmail dot com
2021-09-26 3:40 ` spanksaucee01 at gmail dot com
2021-09-29 13:24 ` schaumburgconcrete at gmail dot com
2021-10-06 3:06 ` jadinvestments1 at gmail dot com
2021-10-06 3:09 ` jadinvestments1 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com [this message]
2021-10-09 17:02 ` studiaviktor at gmail dot com
2021-10-17 11:56 ` ranktowin at gmail dot com
2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com
2021-10-19 7:14 ` progonsaytu at gmail dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-10-27 1:29 ` windsordrywall at gmail dot com
2021-11-02 2:44 ` joanadavidson02 at gmail dot com
2021-11-04 18:08 ` ahbathroomremodel at gmail dot com
2021-11-07 21:13 ` treeservicesask at gmail dot com
2021-11-07 21:19 ` treeservicesask at gmail dot com
2021-11-18 13:58 ` drywallbrantford at protonmail dot com
2021-11-20 3:28 ` fullertonhomepainters at gmail dot com
2021-11-22 6:48 ` gexed96894 at keagenan dot com
2021-11-24 13:42 ` allen at rockvalleymarketing dot com
2021-11-24 17:02 ` cambridgeconcreting 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-27194-4717-n2Yecwzwfr@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).