Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Dmitry Neverov <dmitry.neverov@jetbrains.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PR 31727] Recognize -2 as a tombstone value in .debug_line
Date: Mon, 10 Jun 2024 14:29:15 -0600	[thread overview]
Message-ID: <87jziwilt0.fsf@tromey.com> (raw)
In-Reply-To: <20240608084529.1406412-1-dmitry.neverov@jetbrains.com> (Dmitry Neverov's message of "Sat, 8 Jun 2024 10:45:29 +0200")

>>>>> "Dmitry" == Dmitry Neverov <dmitry.neverov@jetbrains.com> writes:

Dmitry> Commit a8caed5d7faa639a1e6769eba551d15d8ddd9510 handled the tombstone
Dmitry> value -1 used by lld (https://reviews.llvm.org/D81784).  The
Dmitry> referenced lld commit also uses the tombstone value -2 for
Dmitry> pre-DWARF-v5
Dmitry> (https://github.com/llvm/llvm-project/commit/e618ccbf431f6730edb6d1467a127c3a52fd57f7).

Dmitry> If not handled, -2 breaks the pc step range calculation and triggers
Dmitry> the assertion:

Dmitry>   gdb/infrun.c:2794: internal-error: resume_1: Assertion
Dmitry>   `pc_in_thread_step_range (pc, tp)' failed.

Dmitry> This commit adds -2 tombstone value and handles it in the same way as -1.

Dmitry> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31727

I wonder if it's possible to write a test case for this using the DWARF
assembler.

If that looks too hard, though, I wouldn't bother, considering that the
-2 approach is gone from lld now.  In that case the patch is OK:
Approved-By: Tom Tromey <tom@tromey.com>

Tom

  parent reply	other threads:[~2024-06-10 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-08  8:45 Dmitry Neverov
2024-06-08  8:53 ` Dmitry.Neverov
2024-06-10 20:29 ` Tom Tromey [this message]
     [not found]   ` <87cyohxdim.fsf@lubuntu2.mail-host-address-is-not-set>
2024-08-18  6:00     ` [PING][PR " Dmitry.Neverov
2024-08-23 16:16       ` Tom Tromey
2024-09-01 18:50 ` [PR " Joel Brobecker
2024-09-02 17:55   ` Dmitry.Neverov
2024-09-02 18:14     ` Joel Brobecker
2024-09-04 17:58       ` Tom Tromey

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=87jziwilt0.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=dmitry.neverov@jetbrains.com \
    --cc=gdb-patches@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