Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19023
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <001901c5ba69$b6573c70$6c051fac@lighthammer>
To: "RG" <ScriptBlue@nyc.rr.com>
Cc: <internals@lists.php.net>
References: <29.87.41173.A9FD9234@pb1.pair.com> <00f301c5ba49$455192c0$5c8be5a9@ohr.berkeley.edu> <5A.79.43379.A1E1A234@pb1.pair.com>
Date: Thu, 15 Sep 2005 19:09:57 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: Segfault
From: pollita@php.net ("Sara Golemon")

> That's not where it segfaults. The function works perfectly once. If I
> attempt to exit /
> die or call that function again, it segfaults.
> However, I have noticed that if I do not use ZEND_REGISTER_RESOURCE the
> program no longer segfaults.
>
I didn't say that's where it segfaults, I said that's where your problem is. 
Just because you can write to a particular memory location once doesn't 
change the fact that the memory in question doesn't belong to your new_sock 
struct.  Your code is tacking a relevant piece of data and just throwing it 
out into the middle of the memory pool hoping it doesn't hit some swimmer in 
the head in the process.  Figure out why you can't malloc the struct first. 
That one is a very clear, unambiguous crash-causing bug.

> And sorry for the comments, someone people don't write the final version 
> of
> a program on their first try.
>
I'd doubt anyone does.  Writing well-indented code helps debugging though 
(both for you and for people you ask to take a second look).  Right now it's 
all just cluttered.  As my momma always told me, "If you'd clean up your 
room once in awhile, you might find what you're looking for."

And if my reply sounded harsh, it might have to do with the fact that you 
ignored my suggestions on how to implement zend_fetch_list_dtor_id().

-Sara