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 breakpoints/27330] nextoverthrow.exp FAILs on arm-none-eabi
Date: Sat, 09 Oct 2021 11:00:31 +0000 [thread overview]
Message-ID: <bug-27330-4717-TcspfwpJ7W@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27330-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27330
Gulsen Engin <gulsenenginar at aol dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gulsenenginar at aol dot com
--- Comment #15 from Gulsen Engin <gulsenenginar at aol dot com> ---
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint
http://www-look-4.com/computers/huawei-computers/
The test-case nextoverthrow.exp is failing on targets with unstripped libc.
https://komiya-dental.com/category/services/
This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
process_event_stop_test".
http://www.iu-bloomington.com/category/services/
The problem is that this code in create_exception_master_breakpoint:
...
for (objfile *sepdebug = obj->separate_debug_objfile;
https://waytowhatsnext.com/category/services/
sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
if (create_exception_master_breakpoint_hook (sepdebug))
... http://www.wearelondonmade.com/computers/car-computers/
iterates over all the separate debug object files, but fails to handle the
case that obj itself has the debug info we're looking for.
http://www.jopspeech.com/health/nvidia-rtx-2060/
Fix this by using the separate_debug_objfiles () range instead, which does
iterate both over obj and the obj->separate_debug_objfile chain.
http://joerg.li/health/xiaomi/
Tested on x86_64-linux.
http://connstr.net/computers/chargers-tech/
gdb/ChangeLog:
[gdb/breakpoints] Handle glibc with debuginfo in
create_exception_master_breakpoint
http://embermanchester.uk/computers/video-conversation/
The test-case nextoverthrow.exp is failing on targets with unstripped libc.
http://www.slipstone.co.uk/computers/isofix/
This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
process_event_stop_test".
http://www.logoarts.co.uk/computers/printer-types/
The problem is that this code in create_exception_master_breakpoint:
... http://www.acpirateradio.co.uk/technology/facetime/
for (objfile *sepdebug = obj->separate_debug_objfile;
sepdebug != nullptr; sepdebug =
sepdebug->separate_debug_objfile)
if (create_exception_master_breakpoint_hook (sepdebug))
http://www.compilatori.com/computers/smartphones/
...
iterates over all the separate debug object files, but fails to handle the
case that obj itself has the debug info we're looking for.
https://www.webb-dev.co.uk/category/services/
Fix this by using the separate_debug_objfiles () range instead, which does
iterate both over obj and the obj->separate_debug_objfile chain.
Tested on x86_64-linux.
gdb/ChangeLog:
--
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: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 8:53 [Bug breakpoints/27330] New: " vries at gcc dot gnu.org
2021-02-03 8:55 ` [Bug breakpoints/27330] " vries at gcc dot gnu.org
2021-02-03 9:57 ` vries at gcc dot gnu.org
2021-02-05 12:30 ` vries at gcc dot gnu.org
2021-02-05 16:47 ` cvs-commit at gcc dot gnu.org
2021-02-05 19:54 ` cvs-commit at gcc dot gnu.org
2021-02-05 19:55 ` vries at gcc dot gnu.org
2021-06-27 17:44 ` ahmedsayeed1982 at yahoo dot com
2021-09-02 11:06 ` 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-05 7:41 ` vries at gcc dot gnu.org
2021-09-06 9:08 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:38 ` mehmetgelisin at aol dot com
2021-09-20 12:03 ` lisawelch939 at gmail dot com
2021-09-22 10:19 ` diheto5497 at secbuf dot com
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com [this message]
2021-10-09 17:03 ` studiaviktor 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-11-24 13:43 ` allen at rockvalleymarketing 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-27330-4717-TcspfwpJ7W@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).