public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>,
	Andrew Burgess <aburgess@redhat.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb: make "maintenance info line-table" show relocated addresses again
Date: Wed, 22 Mar 2023 09:47:18 -0400	[thread overview]
Message-ID: <dc9787f7-b1f8-6f4b-a2bd-9a26d374db72@simark.ca> (raw)
In-Reply-To: <bff73864-b5ed-b61e-3e8f-ebcd35e3038a@suse.de>



On 3/22/23 09:46, Tom de Vries wrote:
> On 3/22/23 02:35, Simon Marchi via Gdb-patches wrote:
>>
>>> I'm never going to complain about more information.  Especially not in
>>> maintainer commands.
>>>
>>> Just wanted to make sure my use case was noted.
>>
>> Thanks, here's what I pushed.
>>
> 
> I'm seeing regressions, I'm assuming they're due to this patch:
> ...
> Running /data/vries/gdb/src/gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp ...
> FAIL: gdb.dwarf2/dw2-out-of-range-end-of-seq.exp: END with address 1 eliminated
> Running /data/vries/gdb/src/gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp ...
> FAIL: gdb.dwarf2/dw2-ranges-base.exp: count END markers in line table
> Running /data/vries/gdb/src/gdb/testsuite/gdb.base/maint.exp ...
> ERROR: internal buffer is full.
> ERROR: internal buffer is full.

Yeah, I just found that too, looking into it.

Simon

  reply	other threads:[~2023-03-22 13:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 16:30 Simon Marchi
2023-03-20 21:35 ` Andrew Burgess
2023-03-21  1:18   ` Simon Marchi
2023-03-21  9:23     ` Andrew Burgess
2023-03-22  1:35       ` Simon Marchi
2023-03-22 10:26         ` [PATCH 0/1] gdb: Update doc of the "maintenance info line-table" Lancelot SIX
2023-03-22 10:26           ` [PATCH 1/1] " Lancelot SIX
2023-03-22 13:59             ` Simon Marchi
2023-03-22 16:48               ` Lancelot SIX
2023-03-22 17:20               ` [PATCH v2] " Lancelot SIX
2023-03-22 14:58             ` [PATCH 1/1] " Eli Zaretskii
2023-03-22 13:46         ` [PATCH] gdb: make "maintenance info line-table" show relocated addresses again Tom de Vries
2023-03-22 13:47           ` Simon Marchi [this message]
2023-03-22 15:17             ` [PATCH] gdb/testsuite: adjust test cases to previous "maintenance info line-table" change Simon Marchi
2023-03-22 18:01               ` Tom de Vries
2023-03-22 19:14                 ` Simon Marchi

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=dc9787f7-b1f8-6f4b-a2bd-9a26d374db72@simark.ca \
    --to=simark@simark.ca \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=tdevries@suse.de \
    /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).