This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v3] Add debuginfod support to GDB


On Thu, Feb 20, 2020 at 2:43 PM Tom Tromey <tom@tromey.com> wrote:
> >>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
> Simon> Following a discussion on IRC, I changed my mind, the simplest solution
> Simon> for now would be: when the user cancels a download, GDB will continue
> Simon> as if debug info was not available for that objfile.  However, I would suggest
> Simon> printing a message saying that the download of debug info for XYZ was cancelled,
> Simon> so the user is not surprised to not have its debug info.
>
> Wouldn't this imply also clearing (or more precisely - not preserving)
> the quit flag in the interrupt case?
>
> It seems to me that as long as the interrupt is processed by the
> library, then we wouldn't want to set the quit flag again.  Otherwise
> that will look like a double interrupt.

I'm going to change the interrupt handling to not preserve the quit_flag
in cases where the inferior is not running. The download will abort and
gdb will continue as if no debuginfo/source was found. If the inferior is
running and ^C happens during a download, quit_flag will be preserved
and the inferior should see ^C. If ^C happens a second time during the
download then it will abort. This will be accompanied by some help
text so the user knows what's going on. This is my understanding of
what was discussed on IRC.

Aaron


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]