public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dahllunde at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25560] Assertion `pid != 0' failed
Date: Fri, 25 Jun 2021 19:00:59 +0000 [thread overview]
Message-ID: <bug-25560-4717-jWWgQOT5y1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25560-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25560
Vegz78 <dahllunde at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dahllunde at gmail dot com
--- Comment #10 from Vegz78 <dahllunde at gmail dot com> ---
> -> Workaround:
> Now, for what matters, I was able to get gdb-9.2 and Eclipse CDT work
> perfectly by simply swapping 'exec_file_command()' and
> 'symbol_file_command()' inside 'file_command()'. (gdb/exec.c:428)
Thank you very much, @Fil, for your proposed work-around, which is now included
the Homebrew tap domq/gdb/gdb for quick 'n easy installation on MacOS.!
https://github.com/domq/homebrew-gdb
Your work-around handles this bug and the file command error reported in bug
27365, and it's now possible again to debug with gdb both locally on the Mac
and remotely from Visual Studio on Windows.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-25 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25560-4717@http.sourceware.org/bugzilla/>
2020-08-02 15:43 ` delta512.dev at protonmail dot com
2020-08-02 15:46 ` delta512.dev at protonmail dot com
2020-08-02 15:48 ` delta512.dev at protonmail dot com
2020-08-02 15:51 ` delta512.dev at protonmail dot com
2020-08-09 20:33 ` tromey at sourceware dot org
2020-08-10 21:05 ` delta512.dev at protonmail dot com
2020-08-10 21:08 ` delta512.dev at protonmail dot com
2020-08-10 21:14 ` delta512.dev at protonmail dot com
2020-10-20 2:51 ` erickitten at gmail dot com
2020-12-13 13:15 ` ddresser at bmc dot com
2021-06-25 19:00 ` dahllunde at gmail dot com [this message]
2021-06-25 20:56 ` delta512.dev at protonmail dot com
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-25560-4717-jWWgQOT5y1@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).