public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "bbstry at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/27365] New: The "file" command broken
Date: Sun, 07 Feb 2021 14:36:03 +0000	[thread overview]
Message-ID: <bug-27365-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27365
           Summary: The "file" command broken
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: bbstry at 163 dot com
  Target Milestone: ---

My OS is macos mojave 10.14.6, the gdb version is 10.1 and compiled from the
source using default parameters.
When invoke the gdb using command line:
    gdb file_name
it's ok , but when I use file command in gdb shell, it reports:
  thread.c:95: internal-error: struct thread_info *inferior_thread(): Assertion
`current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Then I try to use batch mode to do same work, like this:
   gdb -batch -ex 'file f_add' -ex 'disassemble/rs add'

the same error occured , but when I use the following command line:
   gdb f_add -batch -ex 'disassemble/rs add'

it's OK.

So I think the FILE command in GDB is broken.(In fact, I also used the older
release gdb like version 8.3.1, the gdb file command produced the similar error
like this:
    inferior.c:287: internal-error: struct inferior *find_inferior_pid(int):
Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
And the error has been reported by many people , for example ,the following
link: https://github.com/microsoft/vscode-cpptools/issues/5256 )

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

             reply	other threads:[~2021-02-07 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 14:36 bbstry at 163 dot com [this message]
2021-06-25 19:05 ` [Bug cli/27365] " dahllunde at gmail dot com
2021-07-02 18:46 ` levraiphilippeblain at gmail dot com
2021-07-05  0:57 ` simark at simark dot ca

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