Volt - adding block in page header results in exit signal Segmentation fault (11)

Question

Volt - adding block in page header results in exit signal Segmentation fault (11)

Calin Rada Jun '13

Created Jun '13	Last Reply Jul '13	Replies 5	Views 1216	Votes 2

Calin Rada 51.2k

Jun '13

Hello.

I experienced a strange behavior. If i try to add a block in a page "header", the extension crashes, and in the logs, i can see "...exit signal Segmentation fault (11)"

Example:

<!DOCTYPE HTML> <html lang="en"> <head> <meta charset="utf-8"> <title>Ti</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta name="description" content=""> <meta name="keywords" content=""> <meta name="author" content="[email protected]">

{{ stylesheet_link('assets/admin/default/css/bootstrap.css') }} {{ stylesheet_link('assets/admin/default/css/styles.css') }} {{ stylesheet_link('assets/admin/default/css/bootstrap-responsive.css') }} {{ stylesheet_link('assets/admin/default/css/themes.css') }}

If i try to add {% block your_block_name %}Block content{% endblock %} , anywhere before {{ stylesheet_link('assets/admin/default/css/bootstrap.css') }} , the extension will crash.

Any known issues about this ? Any help would be appreciated. Than you.

Phalcon 1.1.0

2

Calin Rada
51.2k

Accepted
answer

Jul '13

It is working ! Nice ! Thank you very much. If you don't mind, can you tell me in a big view what was all about ? Just curios. Thank you ;}

Phalcon · Answer 1 · 2013-06-28T11:25:37-07:00

Can you try with 1.2.0? maybe the problem is not related to Volt but it's a bug in Phalcon\Escaper in 1.1.0

Calin Rada · Answer 2 · 2013-06-29T03:48:24-07:00

Hello. With 1.2.0 i can't put any {% block %} before </head>. It fails with the same error. If it helps you, i was testing with php 5.4.15 and 5.4.17RC1 on apache, ubuntu 12.04

Calin Rada · Answer 3 · 2013-07-01T02:45:19-07:00

Hi,

I have made a pull now in 1.2.0 and reinstalled phalcon. It seems that this problems is fixed. This are the files with changes:

Calin Rada · Answer 4 · 2013-07-01T06:37:32-07:00

It seems that it is still failing, but for other html section:

        {% for user in users %}
        <tr>
          <td> {{ user.id }} </td>
          <td> {{ user.username }} </td>
        </tr>
        {% endfor %}

If i put the FOR before <table> it works. Like: {% for ... %}<table><tr><td>...</table>{% endfor %}

Calin Rada · Answer 5 · 2013-07-01T06:39:47-07:00

Also, if i generate get and set methods for models and i try to access them in volt ( {{ object.getMethodName() }} ), it throws an error - Access to undefined property Object::getMethodName

Calin Rada · Answer 6 · 2013-07-01T07:24:02-07:00

Update: If i am restarting apache, the first request, renders the page correctly. All the other requests, are failing : "...exit signal Segmentation fault (11)"

Phalcon · Answer 7 · 2013-07-01T08:23:03-07:00

@Calin: Can you please post a full test in a Gist (https://gist.github.com/)?

Follow this example: https://gist.github.com/phalcon/5901789

To properly diagnose the problem, we need a complete script to be able to reproduce the bug ourselves.

Calin Rada · Answer 8 · 2013-07-01T08:56:47-07:00

@Phalcon , please check https://gist.github.com/calinrada/5901923 . I you need anything else, please let me know. Cheers !

Phalcon · Answer 9 · 2013-07-01T10:12:28-07:00

I uploaded your code to https://github.com/phalcon/mvc/tree/master/calinrada

It's running here: https://test.phalcon.io/calinrada/article

Please tell me what to change in the code to see the problem

Calin Rada · Answer 10 · 2013-07-01T11:59:50-07:00

Well, this is the code that is not working for me. So in this case ... ? Maybe it's about apache / APC ? Since the first request after i restart apache is outputing the correct template without errors ?

Phalcon · Answer 11 · 2013-07-01T22:39:53-07:00

We fixed a bug in Volt today that is perhaps related, can you try again compiling from the 1.2.0 branch?

Phalcon · Answer 12 · 2013-07-02T07:31:05-07:00

Long story, it started here: https://github.com/phalcon/cphalcon/pull/745#issuecomment-20255741, it seems it was an uninitialized variable in a recent commit.