| 1 |
On Thursday, November 9, 2017 6:14:26 PM CET Grant Edwards wrote: |
| 2 |
> On 2017-11-09, Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
> > Apologies in advance for the long post, but has anyone else come across |
| 4 |
> > this? |
| 5 |
> > |
| 6 |
> > gen/storage/public/interfaces/blobs.mojom-shared-internal.h:539:5: |
| 7 |
> > internal |
| 8 |
> > compiler error: Segmentation fault |
| 9 |
> > |
| 10 |
> > } |
| 11 |
> > ^ |
| 12 |
> > |
| 13 |
> > Please submit a full bug report, |
| 14 |
> > with preprocessed source if appropriate. |
| 15 |
> > See <https://bugs.gentoo.org/> for instructions. |
| 16 |
> |
| 17 |
> Does it always fault in exactly the same spot? |
| 18 |
> |
| 19 |
> If not... |
| 20 |
> |
| 21 |
> When I've run into "random" gcc segfaults when compiling very large |
| 22 |
> programs, it's always been a hardware problem. Every time except one, |
| 23 |
> it was failing RAM. |
| 24 |
> |
| 25 |
> I'd run memtest86 overnight. |
| 26 |
|
| 27 |
Also check it is not overheating. |
| 28 |
The one time I had random gcc segfaults was when I accidentally forgot decent |
| 29 |
airflow for the CPU about 20+ years ago. |
| 30 |
|
| 31 |
-- |
| 32 |
Joost |
Archives