From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Merge handle_inferior_event and handle_inferior_event_1
Date: Mon, 25 Mar 2019 15:35:00 -0000 [thread overview]
Message-ID: <87a7hjj7aw.fsf@tromey.com> (raw)
In-Reply-To: <87mulnkcab.fsf@redhat.com> (Sergio Durigan Junior's message of "Thu, 21 Mar 2019 20:01:16 -0400")
>>>>> ">" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>> A few days ago (March 18th) a user reported a bug against Fedora GDB:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1690120
>>
>> And, after hours and hours investigating this, I found that your commit
>> actually fixes it. Not sure if it was intended or not, but what a
>> coincidence...
I am curious to know how this change could fix this bug.
That seems mysterious to me.
>> Of course, something I'd also like to ask is: do you think this change
>> is trivial enough to be included in the 8.3 release? I'd like to see it
>> happen. I can create a bug if needed.
I would have thought so but the fact that it causes this behavior makes
me worry a bit. Maybe that's backward!
Tom
next prev parent reply other threads:[~2019-03-25 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190320140846.13031-1-tromey@adacore.com>
2019-03-20 16:21 ` Pedro Alves
2019-03-21 22:05 ` Sergio Durigan Junior
2019-03-22 0:01 ` Sergio Durigan Junior
2019-03-25 15:35 ` Tom Tromey [this message]
2019-03-25 16:34 ` Pedro Alves
2019-03-25 16:46 ` Tom Tromey
2019-03-25 22:20 ` Sergio Durigan Junior
2019-03-26 13:13 ` Tom Tromey
2019-03-26 16:07 ` Sergio Durigan Junior
2019-03-26 18:45 ` Tom Tromey
2019-03-26 21:50 ` Sergio Durigan Junior
2019-03-27 12:57 ` Tom Tromey
2019-03-28 14:12 ` Pedro Alves
2019-03-29 21:44 ` [PATCH] Destroy allocated values when exiting GDB (was: Re: [PATCH] Merge handle_inferior_event and handle_inferior_event_1) Sergio Durigan Junior
2019-04-01 14:08 ` [PATCH] Destroy allocated values when exiting GDB Pedro Alves
2019-04-01 14:59 ` Sergio Durigan Junior
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=87a7hjj7aw.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tromey@adacore.com \
/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