Re: patch 3/3 debuginfod client interruptability

2019-11-19 Thread Mark Wielaard
Hi, On Sun, 2019-11-17 at 21:50 -0500, Frank Ch. Eigler wrote: > > Attached is a variant that adds debuginfod_begin and debuginfo_end > > (names matching elf/dwarf_begin/end) and adds a debuginfod_client > > handle to each other function. > > Sure, if you like. OK, I rebased on the debuginfod-su

Re: patch 3/3 debuginfod client interruptability

2019-11-18 Thread Pedro Alves
On 11/18/19 2:50 AM, Frank Ch. Eigler wrote: >> Attached is a variant that adds debuginfod_begin and debuginfo_end >> (names matching elf/dwarf_begin/end) and adds a debuginfod_client >> handle to each other function. Thanks much for doing this! > > Sure, if you like. Would you be sympathetic t

Re: patch 3/3 debuginfod client interruptability

2019-11-17 Thread Frank Ch. Eigler
Hi - > Attached is a variant that adds debuginfod_begin and debuginfo_end > (names matching elf/dwarf_begin/end) and adds a debuginfod_client > handle to each other function. Sure, if you like. Would you be sympathetic to supporting a client=NULL entrypoint to the lookup functions, ergo no begi

Re: patch 3/3 debuginfod client interruptability

2019-11-17 Thread Mark Wielaard
Hi, On Fri, 2019-11-15 at 18:14 +, Pedro Alves wrote: > On 11/15/19 5:35 PM, Mark Wielaard wrote: > > > IMHO it would be best to avoid any global state from the start. Since > > we haven't released this api yet we can make it so that it is easy to > > have state per request object. > > +1 >

Re: patch 3/3 debuginfod client interruptability

2019-11-15 Thread Pedro Alves
On 11/15/19 5:35 PM, Mark Wielaard wrote: > IMHO it would be best to avoid any global state from the start. Since > we haven't released this api yet we can make it so that it is easy to > have state per request object. +1 > In the gdb thread > https://sourceware.org/ml/gdb-patches/2019-11/msg0

Re: patch 3/3 debuginfod client interruptability

2019-11-15 Thread Mark Wielaard
Hi Aaron, On Fri, 2019-11-15 at 12:03 -0500, Aaron Merey wrote: > On Fri, Nov 15, 2019 at 11:16 AM Mark Wielaard wrote: > > On Mon, 2019-11-04 at 16:48 -0500, Frank Ch. Eigler wrote: > > > At the wise counsel of gdb folks such as and : > > > > > > debuginfod 3/3: client interruptability > >

Re: patch 3/3 debuginfod client interruptability

2019-11-15 Thread Aaron Merey
On Fri, Nov 15, 2019 at 11:16 AM Mark Wielaard wrote: > On Mon, 2019-11-04 at 16:48 -0500, Frank Ch. Eigler wrote: > > At the wise counsel of gdb folks such as and : > > > > debuginfod 3/3: client interruptability > > > > For interactive clients such as gdb, interruptibility is important

Re: patch 3/3 debuginfod client interruptability

2019-11-15 Thread Mark Wielaard
Hi, On Mon, 2019-11-04 at 16:48 -0500, Frank Ch. Eigler wrote: > At the wise counsel of gdb folks such as and : > > debuginfod 3/3: client interruptability > > For interactive clients such as gdb, interruptibility is important for > usability during longer downloads. This patch

patch 3/3 debuginfod client interruptability

2019-11-04 Thread Frank Ch. Eigler
Hi - At the wise counsel of gdb folks such as and : debuginfod 3/3: client interruptability For interactive clients such as gdb, interruptibility is important for usability during longer downloads. This patchset adds a download-progress callback function to the debuginfod c