public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/26289] Infinite loop in dwarf2_attr()
Date: Thu, 23 Jul 2020 08:34:21 +0000	[thread overview]
Message-ID: <bug-26289-4717-yAVS6UqihU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26289-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26289

Andrew Burgess <andrew.burgess at embecosm dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew.burgess at embecosm dot com

--- Comment #2 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
Created attachment 12721
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12721&action=edit
Extended patch including test case

This started out with me "just" writing a test case for this issue. 
Unfortunately this exposed a bunch more places that needed fixing up, so this
is now the original patch + a test case + some additional fixes.

This is still work-in-progress, but the code needs a clean up, and I suspect
that there might be additional test cases that need to be written.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-07-23  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  0:36 [Bug corefiles/26289] New: " leandro at hardinfo dot org
2020-07-23  0:41 ` [Bug corefiles/26289] " leandro at hardinfo dot org
2020-07-23  8:34 ` andrew.burgess at embecosm dot com [this message]
2020-07-23 14:03 ` tromey at sourceware dot org
2023-03-29 14:14 ` [Bug symtab/26289] " tromey at sourceware 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-26289-4717-yAVS6UqihU@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).