Both GCC and GDB buildbot use gcc114

Both GCC and GDB buildbot use gcc114

[Yao Qi]

Hi Paulo,
I noticed that GDB buildbot pending build queue on aarch64-linux
becomes longer and longer,
https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-m64
as it takes longer to finish each build and test.

Looks that you deployed aarch64-linux buildslave for GCC buildbot
on gcc114 as well, that is reason that GDB build and test is slowed
down (GCC build and test is slowed down too).

We'd better avoid using the same machine for two buildbots.  Are there
any easy way to move one buildslave to a different machine like gcc115
or gcc116.  As far as I know, they are identical.

-- 
Yao (齐尧)

Re: Both GCC and GDB buildbot use gcc114

[Paulo Matos]

On 27/02/18 13:53, Yao Qi wrote:
> Hi Paulo,
> I noticed that GDB buildbot pending build queue on aarch64-linux
> becomes longer and longer,
> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-m64
> as it takes longer to finish each build and test.
> 
> Looks that you deployed aarch64-linux buildslave for GCC buildbot
> on gcc114 as well, that is reason that GDB build and test is slowed
> down (GCC build and test is slowed down too).
> 
> We'd better avoid using the same machine for two buildbots.  Are there
> any easy way to move one buildslave to a different machine like gcc115
> or gcc116.  As far as I know, they are identical.
>

Apologies for the clash on resources. Using gcc115 and gcc116 only now.

Kind regards,

-- 
Paulo Matos

Re: Both GCC and GDB buildbot use gcc114

[Yao Qi]

On Tue, Feb 27, 2018 at 9:46 PM, Paulo Matos <pmatos@linki.tools> wrote:
>
> Apologies for the clash on resources. Using gcc115 and gcc116 only now.
>

Thank you, Paulo.

-- 
Yao (齐尧)

Add .gdb_index and CRC mismatch

[Dmitry Antipov]

For the remote debugging and local copies of shared libraries, should .so CRC be affected by
adding .gdb_index as described at https://sourceware.org/gdb/onlinedocs/gdb/Index-Files.html?
After adding .gdb_index, 'target extended-remote :XXXX' refuses to load local copy with
the following message:

warning: the debug information found in "/xxx/yyy/lib/debug/libzzz.so" does not match "target:/lib/libzzz.so" (CRC mismatch).

If CRC was actually changed, how is it indented to use .gdb_index for the remote debugging?
And why there is no CRC warning when I do 'add-symbol-file /xxx/yyy/lib/debug/libzzz.so [addr]' manually?

Dmitry

Re: Add .gdb_index and CRC mismatch

[Jan Kratochvil]

On Thu, 01 Mar 2018 13:41:37 +0100, Dmitry Antipov wrote:
> For the remote debugging and local copies of shared libraries, should .so CRC be affected by
> adding .gdb_index as described at https://sourceware.org/gdb/onlinedocs/gdb/Index-Files.html?
> After adding .gdb_index, 'target extended-remote :XXXX' refuses to load local copy with
> the following message:
> 
> warning: the debug information found in "/xxx/yyy/lib/debug/libzzz.so" does not match "target:/lib/libzzz.so" (CRC mismatch).
> 
> If CRC was actually changed, how is it indented to use .gdb_index for the remote debugging?

At least in Fedora the separate .debug files are also processed by dwz and
then the CRC is updated by:
	/usr/lib/rpm/sepdebugcrcfix

I was expecting the CRC update is needed for dwz and so gdb-add-index does not
contain this functionality.  But you are right it should.

Besides that GDB prefers much faster verification of a .debug file match by
its build-id also being used on Fedora (ld --build-id).  Then sure CRC is not
being checked (as that is slow to check).


Jan