Helmut Grohne 于2018年12月3日周一 上午3:22写道:
>
> On Mon, Dec 03, 2018 at 01:30:43AM +0800, YunQiang Su wrote:
> > YunQiang Su 于2018年12月2日周日 下午11:42写道:
> > >
> > > Matthias Klose 于2018年12月2日周日 下午4:51写道:
> > > >
> > > > On 02.12.18 09:31, Aron Xu wrote:
> > > > > Running with Valgrind shows some errors:
On Mon, Dec 03, 2018 at 01:30:43AM +0800, YunQiang Su wrote:
> YunQiang Su 于2018年12月2日周日 下午11:42写道:
> >
> > Matthias Klose 于2018年12月2日周日 下午4:51写道:
> > >
> > > On 02.12.18 09:31, Aron Xu wrote:
> > > > Running with Valgrind shows some errors:
> > >
> > > that might point to the gcc-search-prefixed
YunQiang Su 于2018年12月2日周日 下午11:42写道:
>
> Matthias Klose 于2018年12月2日周日 下午4:51写道:
> >
> > On 02.12.18 09:31, Aron Xu wrote:
> > > Running with Valgrind shows some errors:
> >
> > that might point to the gcc-search-prefixed-as-ld patch.
yes. with gcc-search-prefixed-as-ld patch removed, it works no
Matthias Klose 于2018年12月2日周日 下午4:51写道:
>
> On 02.12.18 09:31, Aron Xu wrote:
> > Running with Valgrind shows some errors:
>
> that might point to the gcc-search-prefixed-as-ld patch.
It seem not due to this patch,
With some debug, this problem is triggered in gcc/gcc.c
static int
execute (void)
On 02.12.18 09:31, Aron Xu wrote:
> Running with Valgrind shows some errors:
that might point to the gcc-search-prefixed-as-ld patch.
Running with Valgrind shows some errors:
==26292== ERROR SUMMARY: 6 errors from 3 contexts (suppressed: 0 from 0)
==26292==
==26292== 1 errors in context 1 of 3:
==26292== Syscall param stat(file_name) points to unaddressable byte(s)
==26292==at 0x4ABBDD5: _xstat (xstat.c:35)
==26292==by 0
6 matches
Mail list logo