| 1 |
Disabling SEGMEXEC on ld binary solved the problem. Excelent! It can be |
| 2 |
handy for those who still use 32bit in production. It's scary, that |
| 3 |
linking needs so much memory. The top memory usage was just above 1.5G |
| 4 |
(approx 1.548G). Probably both software has just got exceeded 1.5G. |
| 5 |
Without debug. |
| 6 |
|
| 7 |
Thx: |
| 8 |
Dw. |
| 9 |
-- |
| 10 |
dr Tóth Attila, Radiológus, 06-20-825-8057 |
| 11 |
Attila Toth MD, Radiologist, +36-20-825-8057 |
| 12 |
|
| 13 |
2012.Szeptember 7.(P) 14:44 időpontban PaX Team ezt írta: |
| 14 |
> On 7 Sep 2012 at 14:16, "Tóth Attila" wrote: |
| 15 |
> |
| 16 |
>> Omitting "-pipe" from CFLAGS didn't help. What else can I try to compile |
| 17 |
>> these binaries? Are there any PaX or Grsec kernel options with a |
| 18 |
>> potential |
| 19 |
>> influence? |
| 20 |
> |
| 21 |
> i guess you're using SEGMEXEC which limits the process virtual address |
| 22 |
> space |
| 23 |
> size to 1.5G and that is apparently not enough to link these binaries |
| 24 |
> anymore. |
| 25 |
> you can disable SEGMEXEC on the gcc/ld binaries and perhaps USE=-debug if |
| 26 |
> you |
| 27 |
> have it enabled as it can consume more memory at link time for larger |
| 28 |
> binaries. |
| 29 |
> |
| 30 |
> |
| 31 |
> |
Archives