public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/30122] New: [gdb/cli] Add maint check-prologue
@ 2023-02-14 13:36 vries at gcc dot gnu.org
  2023-02-14 13:36 ` [Bug cli/30122] " vries at gcc dot gnu.org
  2023-02-15  9:37 ` vries at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-02-14 13:36 UTC (permalink / raw)
  To: gdb-prs

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

            Bug ID: 30122
           Summary: [gdb/cli] Add maint check-prologue
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I see two conflicting goals:
- we want the testsuite to check prologue analysis
- we don't want to test it in random test-cases, where the intention is
  to check other functionality, which depends on prologue analysis.
  It is both inconvenient and insufficient.

If there is a problem with the prologue analysis, that may be due to a compiler
problem.  In another case, it maybe due to an architecture-specific specific
prologue analyzer.

I've been making test-cases less dependent on prologue analysis, to make
results more similar for different archs/compilers.

But we need to address the fact that this reduces testing of prologue analysis.

I came up with the idea of making a command maint check-prologue that iterates
over all the functions in an exec, calls both the architecture-specific
prologue analysis and the compiler-based prologue analysis and compares then,
and prints a line per function where there's a mismatch.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug cli/30122] [gdb/cli] Add maint check-prologue
  2023-02-14 13:36 [Bug testsuite/30122] New: [gdb/cli] Add maint check-prologue vries at gcc dot gnu.org
@ 2023-02-14 13:36 ` vries at gcc dot gnu.org
  2023-02-15  9:37 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-02-14 13:36 UTC (permalink / raw)
  To: gdb-prs

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
          Component|testsuite                   |cli

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug cli/30122] [gdb/cli] Add maint check-prologue
  2023-02-14 13:36 [Bug testsuite/30122] New: [gdb/cli] Add maint check-prologue vries at gcc dot gnu.org
  2023-02-14 13:36 ` [Bug cli/30122] " vries at gcc dot gnu.org
@ 2023-02-15  9:37 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-02-15  9:37 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Note: related patch: [RFC][gdb] Add maint set skip-prologue (
https://sourceware.org/pipermail/gdb-patches/2022-August/191343.html )

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-02-15  9:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-14 13:36 [Bug testsuite/30122] New: [gdb/cli] Add maint check-prologue vries at gcc dot gnu.org
2023-02-14 13:36 ` [Bug cli/30122] " vries at gcc dot gnu.org
2023-02-15  9:37 ` vries at gcc dot gnu.org

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).