php-general Digest 10 Oct 2012 13:12:27 -0000 Issue 8000
Topics (messages 319392 through 319403):
Re: limiting
319392 by: Matijn Woudt
319393 by: Jim Giner
319394 by: Jim Giner
319395 by: Samuel Lopes Grigolato
319396 by: Jim Giner
319397 by: Tim Streater
319398 by: Govinda
319399 by: Matijn Woudt
319400 by: tamouse mailing lists
319402 by: Ashley Sheridan
319403 by: Andy McKenzie
crash dump on OS X Server: PHP / Apache
319401 by: Mattias Thorslund
Administrivia:
To subscribe to the digest, e-mail:
php-general-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-general-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-gene...@lists.php.net
----------------------------------------------------------------------
--- Begin Message ---
On Tue, Oct 9, 2012 at 9:18 PM, David McGlone <da...@dmcentral.net> wrote:
> On Tuesday, October 09, 2012 12:18:06 PM Jim Giner wrote:
>>
>> Sorry to be so blunt.
>
> It's fine I kinda figured I'd be either ignored, or yelled at when I asked
> and I
> now know that I need to be a professional to ask questions here so there went
> my confidence.
>
> --
> David M.
>
David,
You really don't need to be a professional here to ask questions, but
you can imagine that we're not going to write code for you. Some
people expect professional support here (like they paid for it), and
that's clearly not the case. We are all volunteers with our (limited)
spare time. Therefore, you're expected to figure out most things out
yourself (reading PHP manual, google, etc), and only ask here if you
really can't figure things out. Then you can post what you have tried,
and what you think it should do. For example your previous post, you
could have just looked up what the 'echo' and 'return' statements do
in the PHP manual, and they are probably explained pretty OK in those
books you own too. You probably could have answered the questions you
posted here yourself, after reading PHP manual carefully.
- Matijn
--- End Message ---
--- Begin Message ---
PLEASE SEE MY COMMENTS INTERSPERSED AND BELOW.
(yes this is a top post)
On 10/9/2012 3:18 PM, David McGlone wrote:
On Tuesday, October 09, 2012 12:18:06 PM Jim Giner wrote:
On 10/8/2012 11:11 PM, David McGlone wrote:
Hi all,
is there any other way to limit this code to only displaying 1 image other
than using return. When I use return, I can't get the other images to
display in lightbox, but when I use echo, all 5 of the images will
correctly display in lightbox, but they are also displaying on the page.
$result = mysql_query("SELECT * FROM properties");
$row = mysql_fetch_array($result);
$matches = glob('images/property_pics/212006966/' .$prefix. '*');
foreach($matches as $match){
echo "<a href=$match rel='lightbox[$matches]' /><img src =
$match></a>";
I'm not even sure if this is possible, but thought I'd ask before I
scrapped the idea. I've been at this code since last thursday trying to
learn as much as I can about it and I just keep going in circles and I'm
starting to feel like glob() is what is limiting me. I've tried various
code blocks with things like where(), str_repeat, basename, scandir, sort
etc with no luck. :-/
I hate to sound condescending, but you are showing some serious
deficiencies in your programming ability. I have to say that you are
tackling some very complex processes without the basic understanding of
programming that one needs. What I base this opinion on is that since
you first revealed your lack of understanding of Return and echo in php,
you have spent another 3 days and STILL don't understand? Really?
I was afraid when I first posted that question, it would give that impression.
I've known what echo does, but not very much about return. Also a part of me
has always wondered when I'm studying code from things like wordpress I don't
think I have seen any echo statements. If I did it was very very few. (hint:
why I asked about templeting systems about a month ago.)
As for the code above - once again it looks like you have posted a
re-typing of some code you have tried to execute. I say that because
you have a query and a fetch of one record of the results THAT HAS
NOTHING TO DO WITH THE REST OF THE CODE!
The query is geting a number out of the database and putting the value in
$prefix.
NOT IN THIS SCRIPT!!
Also - you have an array
being used as part of the Rel tag? What's up with that? (I think you
meant to use $match - but that further verifies that this is NOT the
code you ran.)
I tried using $match and $matches because I got confused there for a bit and
changed it.
$MATCH WOULD WORK; $MATCHES WOULD NOT. It's suppose to be a 'name' -
so why would you put an array reference in the Rel attribute?
Finally - the code is (from your description) doing exactly what it is
designed to do (the running code that is).
It sure is, and I found out what my whole problem was this morning before I
went to work. My problem was lightbox was not putting all the images in
$match. but I never suspected it until Matijn and Marco, posted an example of
code and It turned my attention to the piece of code....... put a bunch of
images in a folder and try running the code..... You'll see what I'm talking
about.
THATS' CAUSE YOU DIDN'T LABEL THEM WITH $MATCH!
All the (repeated) "echo"
statements are going to put something on your web page.
Yes I was getting stuff on the page, and then when I'd try and build onto the
idea, and things broke, I'd try something else, and something else, until
finally I'm all confused with it. for example I'd forget to terminate something
and get a blank screen and imediately suspect it was the new code I
introduced. After the millionith time I started realizing when I get a blank
screen, I forgot my semicolon at the end of a line somewhere.
The question
you have is (apparently) how to hide them, since I believe Lightbox is
going to have to have them present in order to do its thing.
That's part of it. the other part is that lighbox is supposed to do that
automatically and it should, and that's another reason I was getting confused.
like I said earlier run the code and you'll see what I'm saying.
I HAVE USED LB - IT DOESN'T HIDE THINGS. IT DISPLAYS THINGS. THINGS
THAT YOU PROVIDE - WHETHER YOU HAVE THEM HIDDEN OR NOT.
Feel free to check out a site I developed - voorheesvilefd.org. This
site uses plenty of php and LB to display random photos drawn from
folders across the site.
And so -
in parting - I think you need to develop some html knowledge to
facilitate that "hiding" part and some immediate skills in the general
area of programming and learning to locate and read the right manuals.
"Glob" is the least of your concerns.
Yes - I'm being rough (I say this to you David as well as the rest of
the community that is still interested in this post) but somebody has to
make you realize that you are seriously in over your head and don't even
know it.
I've said it many times, I am doing this to try and further my knowledge in
PHP and get past the basic echoing of variables and strings, and this is
nothing more than practice.
AGAIN - THE THINGS YOU ARE TRYING ARE WAY BEYOND YOUR CURRENT SKILL LEVELS.
Have you read a book on php and perhaps one on CSS to help
with your "hiding" problem? (BTW - that last was a hint.)
I've read plenty of PHP books I own at least 5 and ALL of them I've read
hardly ever explain anything at all. They just throw some code in there and
say "this is what it does" and gives a picture of the finished product. Total
waste of my money! Also, how am I going to learn PHP if I've got to mix it all
up with CSS. It's just going to make things harder and more confusing on me. I
only threw lightbox in there because I knew I didn't have to do or learn
anything special and to put a smile on my face if it worked. After all, if it
can't be fun, why do it?
YOU HAVE READ THE WRONG BOOKS. FIVE OF THEM AND YOU DIDN'T LEARN THE
DIFF BETWEEN A RETURN AND AN ECHO? Five of them? Really? And you
didn't think to buy a book better than the first two were?
AND PLEASE - don't post supposed "code snippets" again. Let us see what
you really ran if you want us to help.
Or do you not know how to copy
and paste either? I/we can't help you if we can't see it.
That and only that is what I was running. I had changed it so many times
trying to learn that if something was screwed up, it was probably because,
before I posted, I had forgot to change it back.
Sorry to be so blunt.
It's fine I kinda figured I'd be either ignored, or yelled at when I asked and I
now know that I need to be a professional to ask questions here so there went
my confidence.
no you don't need to be a professional. You need to be at least halfway
informed. If you were asking questions about introductory scripts you
would be given the help you need. But you are asking for help with
things that are very complicated and you still haven't learned the
basics. Start from the beginning and work your way up to this. Really.
And if the code you posted here was something you were tinkering with
and lost sight of what you had done, it really shows that you don't have
a lot of understanding of php, arrays, variables or html at all.
Yes - this can be fun. I love creating stuff every chance I get, and I
help people when I can with their problems. But you can't dive into the
deep end until you've learned the doggie paddle at least. Please,
please trust me. If you are a only a few days from having to have
Return and Echo explained to you, you are weeks away from this exercise
ever making sense for you.
So - now that you've had your epiphany from this morning's responses,
what does your script look like now?
--
David M.
--- End Message ---
--- Begin Message ---
On 10/9/2012 3:46 PM, Matijn Woudt wrote:
On Tue, Oct 9, 2012 at 9:18 PM, David McGlone <da...@dmcentral.net> wrote:
On Tuesday, October 09, 2012 12:18:06 PM Jim Giner wrote:
Sorry to be so blunt.
It's fine I kinda figured I'd be either ignored, or yelled at when I asked and I
now know that I need to be a professional to ask questions here so there went
my confidence.
--
David M.
David,
You really don't need to be a professional here to ask questions, but
you can imagine that we're not going to write code for you. Some
people expect professional support here (like they paid for it), and
that's clearly not the case. We are all volunteers with our (limited)
spare time. Therefore, you're expected to figure out most things out
yourself (reading PHP manual, google, etc), and only ask here if you
really can't figure things out. Then you can post what you have tried,
and what you think it should do. For example your previous post, you
could have just looked up what the 'echo' and 'return' statements do
in the PHP manual, and they are probably explained pretty OK in those
books you own too. You probably could have answered the questions you
posted here yourself, after reading PHP manual carefully.
- Matijn
Matijn - well said.
--- End Message ---
--- Begin Message ---
I don't know if it has any value, but here's my 2 cents:
People here expect tricky questions. Of course "to be tricky" is subjective and
is based on your knowledge level. When posting, please try to write every bit
of effort you had so far trying to solve your problem.
Besides that, please, don't feel sad or ignored or whatsoever if the answers
you've got wasn't satisfactory or doesn't came at all. As Matijn said, this
list isn't meant to be a "hand holding" professional support and it may happen
that the ones with the knowledge simply doesn't got the time to help.
Remember that any answer is given with nothing in return, so, read carefully
and follow the wise advices provided by the ones that learned the hard way and
are here today "softening" the path for the newcomers.
Everything should be interpreted as directions and hints, and not as yells or
other bad things, doesn't matter how bad the words appear to be.
Good luck in your path.
-----Mensagem original-----
De: Jim Giner [mailto:jim.gi...@albanyhandball.com]
Enviada em: terça-feira, 9 de outubro de 2012 17:07
Para: php-gene...@lists.php.net
Assunto: Re: [PHP] Re: limiting
On 10/9/2012 3:46 PM, Matijn Woudt wrote:
> On Tue, Oct 9, 2012 at 9:18 PM, David McGlone <da...@dmcentral.net> wrote:
>> On Tuesday, October 09, 2012 12:18:06 PM Jim Giner wrote:
>>>
>>> Sorry to be so blunt.
>>
>> It's fine I kinda figured I'd be either ignored, or yelled at when I
>> asked and I now know that I need to be a professional to ask
>> questions here so there went my confidence.
>>
>> --
>> David M.
>>
>
> David,
>
> You really don't need to be a professional here to ask questions, but
> you can imagine that we're not going to write code for you. Some
> people expect professional support here (like they paid for it), and
> that's clearly not the case. We are all volunteers with our (limited)
> spare time. Therefore, you're expected to figure out most things out
> yourself (reading PHP manual, google, etc), and only ask here if you
> really can't figure things out. Then you can post what you have tried,
> and what you think it should do. For example your previous post, you
> could have just looked up what the 'echo' and 'return' statements do
> in the PHP manual, and they are probably explained pretty OK in those
> books you own too. You probably could have answered the questions you
> posted here yourself, after reading PHP manual carefully.
>
> - Matijn
>
Matijn - well said.
--
PHP General Mailing List (http://www.php.net/) To unsubscribe, visit:
http://www.php.net/unsub.php
--- End Message ---
--- Begin Message ---
On 10/9/2012 4:54 PM, Samuel Lopes Grigolato wrote:
I don't know if it has any value, but here's my 2 cents:
People here expect tricky questions. Of course "to be tricky" is subjective and
is based on your knowledge level. When posting, please try to write every bit of effort
you had so far trying to solve your problem.
Besides that, please, don't feel sad or ignored or whatsoever if the answers you've got
wasn't satisfactory or doesn't came at all. As Matijn said, this list isn't meant to be a
"hand holding" professional support and it may happen that the ones with the
knowledge simply doesn't got the time to help.
Remember that any answer is given with nothing in return, so, read carefully and follow
the wise advices provided by the ones that learned the hard way and are here today
"softening" the path for the newcomers.
Everything should be interpreted as directions and hints, and not as yells or
other bad things, doesn't matter how bad the words appear to be.
Good luck in your path.
-----Mensagem original-----
De: Jim Giner [mailto:jim.gi...@albanyhandball.com]
Enviada em: terça-feira, 9 de outubro de 2012 17:07
Para: php-gene...@lists.php.net
Assunto: Re: [PHP] Re: limiting
On 10/9/2012 3:46 PM, Matijn Woudt wrote:
On Tue, Oct 9, 2012 at 9:18 PM, David McGlone <da...@dmcentral.net> wrote:
On Tuesday, October 09, 2012 12:18:06 PM Jim Giner wrote:
Sorry to be so blunt.
It's fine I kinda figured I'd be either ignored, or yelled at when I
asked and I now know that I need to be a professional to ask
questions here so there went my confidence.
--
David M.
David,
You really don't need to be a professional here to ask questions, but
you can imagine that we're not going to write code for you. Some
people expect professional support here (like they paid for it), and
that's clearly not the case. We are all volunteers with our (limited)
spare time. Therefore, you're expected to figure out most things out
yourself (reading PHP manual, google, etc), and only ask here if you
really can't figure things out. Then you can post what you have tried,
and what you think it should do. For example your previous post, you
could have just looked up what the 'echo' and 'return' statements do
in the PHP manual, and they are probably explained pretty OK in those
books you own too. You probably could have answered the questions you
posted here yourself, after reading PHP manual carefully.
- Matijn
Matijn - well said.
--
PHP General Mailing List (http://www.php.net/) To unsubscribe, visit:
http://www.php.net/unsub.php
And your 2 cents are very well spent too!
Not all questions need to be tricky. Sometimes a new user just hasn't
got something quite right and doesn't see it. Ask away in that case and
the simple error will be pointed out. There are always roadblocks in
the development of a project as well as the development of a programmer.
jg
--- End Message ---
--- Begin Message ---
On 09 Oct 2012 at 20:46, Matijn Woudt <tijn...@gmail.com> wrote:
> For example your previous post, you
> could have just looked up what the 'echo' and 'return' statements do
> in the PHP manual, and they are probably explained pretty OK in those
> books you own too. You probably could have answered the questions you
> posted here yourself, after reading PHP manual carefully.
Here, the phrase "PHP manual" means:
http://www.php.net/manual/en/
which I consider to be an excellent written resource for the language. In fact,
I own no PHP books at all (whereas I do for JavaScript/HTML/CSS/SQLite) so that
must say something about the quality of the on-line documentation. Further, it
is written in a straightforward way, not trying to be clever (unlike some
languages I could mention), so I can recommend it. It's available in languages
other than English, too.
--
Cheers -- Tim
--- End Message ---
--- Begin Message ---
> [snip]
> When posting, please try to write every bit of effort you had so far trying
> to solve your problem.
>
> Besides that, please, don't feel sad or ignored or whatsoever if the answers
> you've got wasn't satisfactory or doesn't came at all. As Matijn said, this
> list isn't meant to be a "hand holding" professional support and it may
> happen that the ones with the knowledge simply doesn't got the time to help.
>
> Remember that any answer is given with nothing in return, so, read carefully
> and follow the wise advices provided by the ones that learned the hard way
> and are here today "softening" the path for the newcomers.
>
> Everything should be interpreted as directions and hints, and not as yells or
> other bad things, doesn't matter how bad the words appear to be.
+1
--- End Message ---
--- Begin Message ---
On Wed, Oct 10, 2012 at 12:06 AM, Tim Streater <t...@clothears.org.uk> wrote:
> On 09 Oct 2012 at 20:46, Matijn Woudt <tijn...@gmail.com> wrote:
>
>> For example your previous post, you
>> could have just looked up what the 'echo' and 'return' statements do
>> in the PHP manual, and they are probably explained pretty OK in those
>> books you own too. You probably could have answered the questions you
>> posted here yourself, after reading PHP manual carefully.
>
> Here, the phrase "PHP manual" means:
>
> http://www.php.net/manual/en/
>
> which I consider to be an excellent written resource for the language. In
> fact, I own no PHP books at all (whereas I do for JavaScript/HTML/CSS/SQLite)
> so that must say something about the quality of the on-line documentation.
> Further, it is written in a straightforward way, not trying to be clever
> (unlike some languages I could mention), so I can recommend it. It's
> available in languages other than English, too.
>
> --
> Cheers -- Tim
>
Thanks Tim! Should have mentioned the URL indeed.
Don't forget that if you want to find the manual page for a function fast, try
http://www.php.net/<function name>
where <function name> is the name you're looking for, so for example
for return, you could use
http://www.php.net/return
And there ya go, PHP manual page for return!
- Matijn
--- End Message ---
--- Begin Message ---
On Tue, Oct 9, 2012 at 5:19 PM, Matijn Woudt <tijn...@gmail.com> wrote:
> On Wed, Oct 10, 2012 at 12:06 AM, Tim Streater <t...@clothears.org.uk> wrote:
>> On 09 Oct 2012 at 20:46, Matijn Woudt <tijn...@gmail.com> wrote:
>>
>>> For example your previous post, you
>>> could have just looked up what the 'echo' and 'return' statements do
>>> in the PHP manual, and they are probably explained pretty OK in those
>>> books you own too. You probably could have answered the questions you
>>> posted here yourself, after reading PHP manual carefully.
>>
>> Here, the phrase "PHP manual" means:
>>
>> http://www.php.net/manual/en/
>>
>> which I consider to be an excellent written resource for the language. In
>> fact, I own no PHP books at all (whereas I do for
>> JavaScript/HTML/CSS/SQLite) so that must say something about the quality of
>> the on-line documentation. Further, it is written in a straightforward way,
>> not trying to be clever (unlike some languages I could mention), so I can
>> recommend it. It's available in languages other than English, too.
>>
>> --
>> Cheers -- Tim
>>
>
> Thanks Tim! Should have mentioned the URL indeed.
> Don't forget that if you want to find the manual page for a function fast, try
> http://www.php.net/<function name>
> where <function name> is the name you're looking for, so for example
> for return, you could use
> http://www.php.net/return
> And there ya go, PHP manual page for return!
>
> - Matijn
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
The problems don't seem to be quite in understanding PHP, but
programming in general. O'Reilly this week has a special offer going
on books on general programming, which I hope no one minds if i spam
it in here:
<
http://shop.oreilly.com/category/deals/geek-code-owo.do?code=WKGKCD&imm_mid=0975a3&cmp=em-code-books-videos-geek-code-elist
>
The code is WKGKCD, which should automatically be applied.
Disclaimer: I am not an employee or stakeholder in O'Reilly, I just
like their books an awful lot, and they've helped me a great deal.
That said, I have to say I only own 1 PHP book: PHP Cookbook, which I
think is buried under quite a pile of stuff as I never have used it.
Yes, the online PHP docu is *that* *good*.
--- End Message ---
--- Begin Message ---
Matijn Woudt <tijn...@gmail.com> wrote:
>On Wed, Oct 10, 2012 at 12:06 AM, Tim Streater <t...@clothears.org.uk>
>wrote:
>> On 09 Oct 2012 at 20:46, Matijn Woudt <tijn...@gmail.com> wrote:
>>
>>> For example your previous post, you
>>> could have just looked up what the 'echo' and 'return' statements do
>>> in the PHP manual, and they are probably explained pretty OK in
>those
>>> books you own too. You probably could have answered the questions
>you
>>> posted here yourself, after reading PHP manual carefully.
>>
>> Here, the phrase "PHP manual" means:
>>
>> http://www.php.net/manual/en/
>>
>> which I consider to be an excellent written resource for the
>language. In fact, I own no PHP books at all (whereas I do for
>JavaScript/HTML/CSS/SQLite) so that must say something about the
>quality of the on-line documentation. Further, it is written in a
>straightforward way, not trying to be clever (unlike some languages I
>could mention), so I can recommend it. It's available in languages
>other than English, too.
>>
>> --
>> Cheers -- Tim
>>
>
>Thanks Tim! Should have mentioned the URL indeed.
>Don't forget that if you want to find the manual page for a function
>fast, try
>http://www.php.net/<function name>
>where <function name> is the name you're looking for, so for example
>for return, you could use
>http://www.php.net/return
>And there ya go, PHP manual page for return!
>
>- Matijn
>
>--
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, visit: http://www.php.net/unsub.php
It also has the option to integrate as a search engine option within your
browser too, so you can search right from the search bar without having to go
to the site first; a feature I use all the time.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--- End Message ---
--- Begin Message ---
<snip>
>> Have you read a book on php and perhaps one on CSS to help
>> with your "hiding" problem? (BTW - that last was a hint.)
>
> I've read plenty of PHP books I own at least 5 and ALL of them I've read
> hardly ever explain anything at all. They just throw some code in there and
> say "this is what it does" and gives a picture of the finished product. Total
> waste of my money! Also, how am I going to learn PHP if I've got to mix it all
> up with CSS. It's just going to make things harder and more confusing on me. I
> only threw lightbox in there because I knew I didn't have to do or learn
> anything special and to put a smile on my face if it worked. After all, if it
> can't be fun, why do it?
</snip>
I rarely post anything to this list, because almost everything asked
is above my level of understanding. But, speaking as a relative
beginner, I have a few comments here.
1) Books. I, too, have read a lot of PHP books. In the end, the ones
I've found most useful were by WROX press. Their "Beginning PHP4" by
Choi, Kent, Lea, Prasad, and Ullman was one of the best "intro to
programming" type books I've found for the way I learn. It's now
obsolete, but the core information is still good. I haven't read
through the Beginning PHP 5.3 version as thoroughly, but it also seems
to be pretty good. You might also want to check with local community
colleges to see if someone offers a basic course -- PHP, C, C++,
something like that. The language may be different, but the concepts
remain the same.
2) "They just throw some code in there and say "this is what it does"
and gives a picture of the finished product. Total waste of my money!
Also, how am I going to learn PHP if I've got to mix it all up with
CSS."
This one's harder. These days CSS is part of the web, and you're
stuck with it if you want to do anything complex. So here's my
advice: Find something simple to experiment with. Don't start with a
complex project, start with something that doesn't actually do
anything useful. When I start trying to understand a function I
haven't used before, I build a new page called something like
"foo_test", where foo is the name of the function. These days it
might be ip2long_test, or something like that, but I still have some
in my test folder with names like "echo_test.php" where I was trying
to figure out how that function worked. Start there. Do something
simple. Lightbox may be too complex. Maybe build a fortune cookie
webpage, where every time you click a button it reloads with a new
fortune. Learn to pull fortunes out of a file and out of a database.
Once you've got the hang of that, start using CSS to change how it
looks. Once THAT's working right, figure out how to use JavaScript
(you're going to need it sooner or later!) and AJAX to make it reload
the fortune without reloading the whole page.
Yeah, it's a boring project. But it's a stepping stone to doing
what you really want to do. The alternative is to do what I did:
start with a big project, and accept that you're going to rewrite it
dramatically later. I started with a book inventory system. First I
built a login and authentication system -- that builds a form, and
queries the database to see if the userid and password are correct.
Then I built a system to list what was in the book table for the
database. Around the time I finished that, I realized I needed more
granularity in user logins, so I went back and rebuilt the login tool.
Then I realized I didn't actually have a way to add stuff to the DB,
so I built that tool.... and so on. It ended up taking me something
like a year, because I'd never looked at PHP before, and I've now
scrapped the entire project and rebuilt it. Why? Because I did just
about everything wrong. It just plain wasn't practical to try to fix
it. I'd never learned the basics, I just threw myself at a big
project to see what would happen.
Good luck!
-Andy McKenzie
--- End Message ---
--- Begin Message ---
Perhaps someone can read this backtrace.
This is a problem that causes Apache to not send any output at all.
Doing a die() just before one particular require_once prevents the
issue. If I move that die() into the required file and place it just
after the opening PHP tag, I get the error again. I have verified the
PHP syntax of this file with php -l .
This site uses CodeIgniter and FileMaker's PHP API, and the include file
where this happens is one of the API files. The PHP library is the one
supplied by FileMaker 12 Advanced Server. Another PHP application on the
same server, using the same FileMaker API is running just fine, but that
one isn't using CodeIgniter.
Any insight would be greatly appreciated.
Mattias
Process: httpd [9018]
Path: /usr/sbin/httpd
Identifier: httpd
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: httpd [7101]
Date/Time: 2012-10-09 17:57:11.216 -0700
OS Version: Mac OS X Server 10.6.8 (10K549)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libphp5.so 0x000000010131fe1c _zend_mm_alloc_int +
924
1 libphp5.so 0x0000000101332d4b init_op_array + 113
2 libphp5.so 0x0000000101319be7 compile_file + 218
3 libphp5.so 0x0000000101196ec1 phar_compile_file +
844
4 libphp5.so 0x000000010131923b compile_filename +
190
5 libphp5.so 0x000000010136925d
ZEND_INCLUDE_OR_EVAL_SPEC_TMP_HANDLER + 714
6 libphp5.so 0x000000010135f6b9 execute + 585
7 libphp5.so 0x0000000101330f7c zend_call_function +
2223
8 libphp5.so 0x000000010133199a
call_user_function_ex + 76
9 libphp5.so 0x000000010133b856 zend_error + 1794
10 libphp5.so 0x000000010130e216 zendparse + 8810
11 libphp5.so 0x0000000101319bfb compile_file + 238
12 libphp5.so 0x0000000101196ec1 phar_compile_file +
844
13 libphp5.so 0x00000001013691d8
ZEND_INCLUDE_OR_EVAL_SPEC_TMP_HANDLER + 581
14 libphp5.so 0x000000010135f6b9 execute + 585
15 libphp5.so 0x0000000101330f7c zend_call_function +
2223
16 libphp5.so 0x0000000101261feb
zif_call_user_func_array + 111
17 libphp5.so 0x00000001013600ab
zend_do_fcall_common_helper_SPEC + 2401
18 libphp5.so 0x000000010135f6b9 execute + 585
19 libphp5.so 0x000000010133a8c4 zend_execute_scripts
+ 376
20 libphp5.so 0x00000001012ebf95 php_execute_script +
732
21 libphp5.so 0x00000001013b7612 php_handler + 1237
22 httpd 0x00000001000012cf ap_run_handler + 90
23 httpd 0x0000000100001bc8 ap_invoke_handler +
354
24 httpd 0x000000010002ebd0 ap_process_request +
103
25 httpd 0x000000010002b3b4
ap_process_http_connection + 116
26 httpd 0x00000001000128ac
ap_run_process_connection + 90
27 httpd 0x0000000100012d7a
ap_process_connection + 91
28 httpd 0x0000000100035fbe child_main + 1257
29 httpd 0x000000010003617d make_child + 329
30 httpd 0x0000000100036403
perform_idle_server_maintenance + 498
31 httpd 0x000000010003692d ap_mpm_run + 1246
32 httpd 0x00000001000098f4 main + 2868
33 httpd 0x0000000100000934 start + 52
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x000000000000000d rcx: 0x0000000000000000
rdx: 0x0000000000000359
rdi: 0x0000000000000002 rsi: 0x0000000101d00950 rbp: 0x00007fff5fbfc3f0
rsp: 0x00007fff5fbfc3b0
r8: 0x000000010087f8f0 r9: 0x000000000000000c r10: 0x0000000000000001
r11: 0x0000000101d6c5b0
r12: 0x0000000101d00928 r13: 0x0000000101d00928 r14: 0x000000010087f200
r15: 0x0000000000001e10
rip: 0x000000010131fe1c rfl: 0x0000000000000206 cr2: 0x0000000000000000
Binary Images:
0x100000000 - 0x10004bfe7 +httpd ??? (???)
<36669387-22E7-3D70-2384-46243282B4CC> /usr/sbin/httpd
0x10007f000 - 0x1000a7ff7 libpcre.0.dylib 1.1.0 (compatibility 1.0.0)
<61E04B84-398D-0E87-7125-A668E797DE77> /usr/lib/libpcre.0.dylib
0x1000ac000 - 0x1000c4fe7 libaprutil-1.0.dylib 4.9.0 (compatibility
4.0.0) <EE4E295F-B414-930C-4CFA-0D2E1265A5FC> /usr/lib/libaprutil-1.0.dylib
--- End Message ---
