public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "Samuel.r.warner at me dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/26912] "file" command causes core dump while specifying the executable on the command line does not
Date: Sat, 03 Jul 2021 17:25:17 +0000 [thread overview]
Message-ID: <bug-26912-4717-lE48k5h6iQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26912-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26912
--- Comment #13 from Sam Warner <Samuel.r.warner at me dot com> ---
Hi Simon,
I’ve been unable to find this patch on
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git
<https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git> I tried searching
based on Change-ID, and other items listed within the thread, and even your
name. Can you point me to the patch?
You do show the source changes you made. I will go make the source changes
to solid-darwin.c and test. If you can point me to the patch that’d be great.
Sam
> On Jul 2, 2021, at 3:51 PM, simark at simark dot ca <sourceware-bugzilla@sourceware.org> wrote:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26912
>
> --- Comment #11 from Simon Marchi <simark at simark dot ca> ---
> (In reply to Sam Warner from comment #9)
>> Can I change the bug to Confirmed and assign myself (WIP on using Simon's
>> source modifications (simark), and if not resolved by these continue to
>> investigate-resolve)?
>
> Here's the patch in question:
>
> https://sourceware.org/pipermail/gdb-patches/2021-June/180396.html
>
> Can you just verify if this fixes the problem for you? If so I'll commit it to
> the master branch.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-03 17:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 0:44 [Bug c++/26912] New: " jim.pirman at gmail dot com
2020-11-18 0:50 ` [Bug c++/26912] " jim.pirman at gmail dot com
2020-12-02 21:58 ` aaroncarsonart at gmail dot com
2020-12-02 22:03 ` aaroncarsonart at gmail dot com
2020-12-02 22:06 ` simark at simark dot ca
2020-12-03 1:08 ` aaroncarsonart at gmail dot com
2020-12-03 17:07 ` simark at simark dot ca
2020-12-14 19:05 ` simark at simark dot ca
2021-01-20 11:47 ` jrbalsas at ujaen dot es
2021-02-11 0:09 ` egad at uottawa dot ca
2021-07-02 18:50 ` Samuel.r.warner at me dot com
2021-07-02 18:53 ` Samuel.r.warner at me dot com
2021-07-02 18:55 ` Samuel.r.warner at me dot com
2021-07-02 22:50 ` simark at simark dot ca
2021-07-02 22:51 ` simark at simark dot ca
2021-07-02 23:07 ` Samuel.r.warner at me dot com
2021-07-03 17:25 ` Samuel.r.warner at me dot com [this message]
2021-07-03 18:35 ` Samuel.r.warner at me dot com
2021-07-05 0:57 ` simark at simark dot ca
2021-07-05 0:57 ` simark at simark dot ca
2021-07-05 16:04 ` Samuel.r.warner at me dot com
2021-07-05 16:54 ` simark at simark dot ca
2021-07-05 20:45 ` Samuel.r.warner at me dot com
2021-07-05 21:21 ` simark at simark dot ca
2021-07-06 1:18 ` jonah at kichwacoders dot com
2021-07-06 15:56 ` Samuel.r.warner at me dot com
2021-07-06 23:30 ` Samuel.r.warner at me 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-26912-4717-lE48k5h6iQ@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).