On 05/15/13 10:26, Vadim Zhukov wrote:
15.05.2013 11:55 пользователь "Martijn van Duren" <[email protected]
<mailto:[email protected]>> написал:
>
> Hello ports@,
>
> since a couple of weeks now I have runtime errors when running
> firefox20. At first I thought that it might be that something went wrong
> when keeping my system at -current.
> Monday I reinstalled my system because of this issue, but the error
> remains.
> When opening with GDB I can't get a full backtrace (since it's not the
> debug-versio), but it does give errors on libxul.
>
> I also tried it both with and without dbus/avahi running, both end in
> the same issue.
>
> I also tried to build it with FLAVOR=debug, but it still exits with a
> Memory Exhausted error. My ulimit settings are:
> # ulimit -a
> time(cpu-seconds) unlimited
> file(blocks) unlimited
> coredump(blocks) unlimited
> data(kbytes) 2097152
> stack(kbytes) 32768
> lockedmem(kbytes) unlimited
> memory(kbytes) unlimited
> nofiles(descriptors) 7030
> processes 1310
>
> Everything is installed via pkg_add and the system is build from a fresh
> checkout from last monday +/- 19:00+02
>
> If someone can help me solve this issue, that would be much appreciated.
>
> Thanks in advance for the help.
>
> Sincerely,
>
> Martijn van Duren
Try to move "i386" from MODCLANG_ARCHS to MODGCC4_ARCHS, run "make
clean" and then rebuild. Thus helped me in a similar issue.
After an hour of online gaming, I think I can safely say that building
it with gcc4.6 fixes this issue for me.
Unfortunately I don't seem to be able to build firefox-debug with clang,
because of Memory Exhausted issues, so I can't trace the problem.
If more people experience this problem on i386 it might be wise to
switch www/mozilla-firefox back to gcc for this architecture.
