Re: [PATCH] Replace some xmalloc-family functions with XNEW-family ones

Simon Marchi
2015-08-26T19:24:38Z

On 15-08-19 11:31 AM, Simon Marchi wrote:
>> If arch-specific files are changes, we have several ways to make sure
>> changes don't break build at least,
>>
>> - Configure gdb with --enable-targets=all --enable-64-bit-bfd and
>> build, all *-tdep.c changes can be covered,
>> - Download some cross compile, such as arm/aarch64/mips gcc, and cross
>> compile native gdb for these archs, for example, configure gdb with
>> --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf CC=/foo/bar/arm-linux-gnueabihf-gcc
>> - Install mingw32 toolchain, and cross compile native gdb for win32.
>>
>> You can also apply for gcc compile farm account to build patched GDB
>> there. The complains of buildbot or people are the last guards, and we
>> should trigger as less complains as we can.
>
> I already build with --enable-targets=all.
>
> Is there a list of cross-compilers we can download to test building gdb
> with ? If you guys have links to already built cross-compilers to various
> architectures, I can create a wiki page for it. Otherwise, I'll try to
> build a few toolchains using crosstool-ng, it seems relatively easy.

I was able to test with just a few targets, those for which I was able to
build a toolchain with crosstool-ng (arm and mips). I did mingw32 as well.

I applied for an access to the gcc compile farm, but I'm still waiting.

I don't think I can do better at the moment. Is there still something
holding back the patch?