Ashish SHUKLA wrote:
> Daniel O'Connor writes:
>> On Thursday 05 March 2009 02:44:14 Ashish SHUKLA wrote:
>>> Hi everone,
>>>
>>> While trying to update my 'qt4-gui' port, gcc segfaults during
>>> compilation. I'm running FreeBSD 7.1-STABLE (amd64 architecture) updated
>>> on 3rd March, 2009.
>
On Tue, Mar 03, 2009 at 02:29:21PM +0100, Ivan Voras wrote:
> nico...@boiteameuh.org wrote:
> >
> > IPC Sys5 isn't "64bit-aware" or the problem is elsewhere?
> Yes, SYSVSHM is limited to 2 GB in 7.1. It has recently been extended in
> -CURRENT, it will probably be MFC-ed to 7-STABLE (7.2) soon.
On 2009-Mar-02 23:07:30 +0100, nico...@boiteameuh.org wrote:
>It's seems I can't allocate a shared memory segment more than 2GB.
>I tune sysctl ipc.shm* values but without effects.
>
>IPC Sys5 isn't "64bit-aware" or the problem is elsewhere?
SysV shm doesn't make it clear whether segments can exce
On Thursday 05 March 2009 11:48:11 am Mark Atkinson wrote:
> Ashish SHUKLA wrote:
>
> > Daniel O'Connor writes:
> >> On Thursday 05 March 2009 02:44:14 Ashish SHUKLA wrote:
> >>> Hi everone,
> >>>
> >>> While trying to update my 'qt4-gui' port, gcc segfaults during
> >>> compilation. I'm running
John Baldwin writes:
> On Thursday 05 March 2009 11:48:11 am Mark Atkinson wrote:
>> Ashish SHUKLA wrote:
>>
>> > Daniel O'Connor writes:
>> >> On Thursday 05 March 2009 02:44:14 Ashish SHUKLA wrote:
>> >>> Hi everone,
>> >>>
>> >>> While trying to update my 'qt4-gui' port, gcc segfaults during
>
Forgot to attach the logs from the last mail.
--
Ashish SHUKLA
pgpH53VaKJM1m.pgp
Description: PGP signature
boot.old.log.gz
Description: old boot log
boot.new.log.gz
Description: new boot log
___
freebsd-stable@freebsd.org mailing list
http://list
Ahoy. I recently upgraded an amd64 machine to 7.1-RELEASE, and started
getting a bunch of these at a pretty high frequency (a few hours to a
day apart):
http://acm.poly.edu/~spawk/IMG00033.jpg
The "current process" is always httpd. They're particularly annoying
because the machine doesn't act
