Quoting Andre McCurdy :
On Mon, Jul 19, 2021 at 5:06 PM Ross Burton wrote:
On Fri, 16 Jul 2021 at 20:10, Robert P. J. Day
wrote:
> colleague just asked me what it would take to generate an image
> where the executables and libraries contain all the gdb-related
> debugging info in the
On Mon, Jul 19, 2021 at 5:06 PM Ross Burton wrote:
> On Fri, 16 Jul 2021 at 20:10, Robert P. J. Day wrote:
> > colleague just asked me what it would take to generate an image
> > where the executables and libraries contain all the gdb-related
> > debugging info in the same files (that is, not
On Fri, 16 Jul 2021 at 20:10, Robert P. J. Day wrote:
> colleague just asked me what it would take to generate an image
> where the executables and libraries contain all the gdb-related
> debugging info in the same files (that is, not broken out in the
> .debug directories).
>
> i pointed out
On Fri, 16 Jul 2021, Khem Raj wrote:
> On Fri, Jul 16, 2021 at 12:10 PM Robert P. J. Day
> wrote:
> >
> >
> > colleague just asked me what it would take to generate an image
> > where the executables and libraries contain all the gdb-related
> > debugging info in the same files (that is, not
On Fri, Jul 16, 2021 at 12:10 PM Robert P. J. Day wrote:
>
>
> colleague just asked me what it would take to generate an image
> where the executables and libraries contain all the gdb-related
> debugging info in the same files (that is, not broken out in the
> .debug directories).
>
> i
colleague just asked me what it would take to generate an image
where the executables and libraries contain all the gdb-related
debugging info in the same files (that is, not broken out in the
.debug directories).
i pointed out that this would increase the size of the installable
target
