Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: domain of trawick@gmail.com designates
 64.233.170.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=JoR6YRBzPkISSajuqtUhvHESS4wp+icjwlpaLnzrwcL/J+cQK0wjv8PLbVQ3YsD8nN+9btHrqE4W0I61j/v1d0lZcRDKcOxCJHSRngzOOyj7r9NP1kmn087hbbDO+MMkVREVkvqnPzJB9rgAjdCKSFVp0vo5PCfC/aRK2AHCUK8=
Message-ID: <cc67648e050107092299430d5@mail.gmail.com>
Date: Fri, 7 Jan 2005 12:22:47 -0500
From: Jeff Trawick <trawick@gmail.com>
Reply-To: Jeff Trawick <trawick@gmail.com>
To: APR Development <dev@apr.apache.org>
Subject: Re: apr_global_mutex_create never returns
In-Reply-To: <41DEBD26.1090601@404ster.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <41DEA390.7050207@404ster.com>
	 <cc67648e05010707113cb454b@mail.gmail.com>
	 <41DEBD26.1090601@404ster.com>

On Fri, 07 Jan 2005 08:47:34 -0800, Jeff Walter <jeff@404ster.com> wrote:
> Jeff Trawick wrote:
> > what is the backtrace?  (attach with debugger)
> 
> Funny... I didn't notice it before, my apr_shm_create causes a segfault
> (when I remove the file that actually gets created the run before).  A
> trace...
> 
> open("/var/lib/mod_straw/mod_straw.shm", O_WRONLY|O_CREAT|O_EXCL, 0666) = 35
> stat64("/var/lib/mod_straw/mod_straw.shm", {st_mode=S_IFREG|0644,
> st_size=0, ...}) = 0
> shmget(17008977, 20800, IPC_CREAT|IPC_EXCL|0600) = 4030469
> shmat(4030469, 0, 0)                    = 0x411e4000
> shmctl(4030469, IPC_64|IPC_STAT, 0xbffff9d0) = 0
> getuid32()                              = 0
> getgid32()                              = 0
> shmctl(4030469, IPC_64|IPC_SET, 0xbffff9d0) = 0
> write(35, "@Q\0\0", 4)                  = 4
> close(35)                               = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---

please run it from the debugger to see which line of code is crashing...