public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/30252] gdb-13.1/gdb/target.c:2641: internal-error: target_resume: Assertion `inferior_ptid != null_ptid' failed
Date: Thu, 06 Jul 2023 14:10:26 +0000	[thread overview]
Message-ID: <bug-30252-4717-peSBxScVRk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30252-4717@http.sourceware.org/bugzilla/>

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

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b2ad7bb9e6a012699195d3eda9d40679c406ebdc

commit b2ad7bb9e6a012699195d3eda9d40679c406ebdc
Author: Pedro Alves <pedro@palves.net>
Date:   Thu Jul 6 15:05:11 2023 +0100

    Fix Solaris regression (PR tdep/30252)

    PR tdep/30252 reports that using GDB on Solaris fails an assertion in
    target_resume:

     target.c:2648: internal-error: target_resume: Assertion `inferior_ptid !=
null_ptid' failed.
     A problem internal to GDB has been detected,
     further debugging may prove unreliable.
     Quit this debugging session? (y or n)

    The backtrace, after running it through c++filt, looks like:

     ----- Backtrace -----
     0xa18914 gdb_internal_backtrace_1
             /root/binutils-gdb/gdb/bt-utils.c:122
     0xa18914 gdb_internal_backtrace()
             /root/binutils-gdb/gdb/bt-utils.c:168
     0xdec834 internal_vproblem
             /root/binutils-gdb/gdb/utils.c:401
     0xdecad8 internal_verror(char const*, int, char const*, __va_list_tag*)
             /root/binutils-gdb/gdb/utils.c:481
     0xf3638c internal_error_loc(char const*, int, char const*, ...)
             /root/binutils-gdb/gdbsupport/errors.cc:58
     0xd70580 target_resume(ptid_t, int, gdb_signal)
             /root/binutils-gdb/gdb/target.c:2648
     0xc59e85 procfs_target::wait(ptid_t, target_waitstatus*,
enum_flags<target_wait_flag>)
             /root/binutils-gdb/gdb/procfs.c:2187
     0xcf6da7 sol_thread_target::wait(ptid_t, target_waitstatus*,
enum_flags<target_wait_flag>)
             /root/binutils-gdb/gdb/sol-thread.c:442
     0xd73711 target_wait(ptid_t, target_waitstatus*,
enum_flags<target_wait_flag>)
             /root/binutils-gdb/gdb/target.c:2586
     ...

    The problem is that the procfs backend, while inside target_wait,
    called target_resume without switching to the leader thread of that
    resumption.

    The target_resume interface is:

     /* Resume execution (or prepare for execution) of the current thread
        (INFERIOR_PTID), while optionally letting other threads of the
        current process or all processes run free.
        ...

    Thus calling target_resume with inferior_ptid == null_ptid is bogus.

    target_wait (which leads to procfs_target::wait on Solaris) is called
    with inferior_ptid == null_ptid on entry exactly to help catch such
    bogus uses.

    From the backtrace, it seems that the relevant line in question is
    procfs.c:2187:

    2186  /* How to keep going without returning to wfi: */
    2187  target_continue_no_signal (ptid);
    2188  goto wait_again;

    target_continue_no_signal is a small wrapper around target_resume,
    which would make sense.

    The fix is to not call target_resume or go via the target stack at
    all.  Instead, factor out a new proc_resume function out of
    procfs_target::resume, and call that.  The new function does not rely
    on inferior_ptid.

    I've not been able to test it myself, but Petr confirmed it fixes the
    assertion failure with his test case, and Marcel Telka also confirmed
    it solves the problem.

    Tested-By: Petr Å umbera <petr.sumbera@oracle.com>
    Tested-By: Marcel Telka <marcel@telka.sk>
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30252
    Change-Id: I6213c59b081d400a22e799ee621c2eff6dcafbf3

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

  parent reply	other threads:[~2023-07-06 14:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 16:00 [Bug gdb/30252] New: " petr.sumbera at oracle dot com
2023-03-20 16:01 ` [Bug gdb/30252] " petr.sumbera at oracle dot com
2023-03-21  9:08 ` petr.sumbera at oracle dot com
2023-03-21 14:55 ` [Bug tdep/30252] " tromey at sourceware dot org
2023-03-22  1:02 ` simark at simark dot ca
2023-03-22  8:06 ` petr.sumbera at oracle dot com
2023-03-23 16:13 ` pedro at palves dot net
2023-03-23 17:36 ` pedro at palves dot net
2023-03-24  8:06 ` petr.sumbera at oracle dot com
2023-06-12 20:16 ` marcel at telka dot sk
2023-07-06 14:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-06 14:12 ` cvs-commit at gcc dot gnu.org
2023-07-06 14:15 ` pedro at palves dot net

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-30252-4717-peSBxScVRk@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).