|
From: Philippe W. <phi...@sk...> - 2023-01-09 23:36:18
|
On Mon, 2023-01-09 at 08:53 +0100, Paul Floyd wrote: > Hi Phlippe > > On 09-01-23 06:06, Philippe Waroquiers wrote: > > > I have just pushed changes to filter_gdb.in and filter_vgdb.in as this failure > > is quite general. > > OK but the change doesn't seem to have landed yet. My bad, I thought I pushed it. Now, I (really) pushed the changes. Next nightly builds should be better ... > > > > I have tested this on gcc186 where gdbserver tests were failing before the above updates, > > and now they are ok. > > > > Should fix the tests on FreeBSD also. > > > > When GDB can read your .gdbinit, setting the auto-load safe path should allow to load > > the python code. > > Unfortunately I think that there is a problem on FreeBSD. Does GDB load the python code on FreeBSD from a 'make install' launched valgrind, with .gdbinit allowing auto-load ? > As already > said there is an issue on a clean system when running in the build > directory. Because the auto-load uses VG_LIBDIR which is based on the > configure -prefix rather than the in-place location the scripts won't > load if you haven't done a make install. Effectively, the python code will be loaded only from the installation directory. > > The same should hold for the nightly tests. The script does a make / > make check / make install and then a make regtest in the build dir. So > that should work. > > I also see that several of the Linux nightlies also have failures. What I just pushed should make them work again. > > A+ > Paul |