terminated by signal SIGSEGV (Address boundary error) #5

Closed
lepture opened this Issue Nov 18, 2013 · 7 comments

Comments

Projects
None yet
5 participants
@lepture
Contributor

lepture commented Nov 18, 2013

It will always break on Mac OS with this message:

Job 1, 'python tests/hoedown_test.py' terminated by signal SIGSEGV (Address boundary error)

Maybe it is hoedown's bug.

@hhatto

This comment has been minimized.

Show comment
Hide comment
@hhatto

hhatto Nov 19, 2013

Owner

in progress...

error output
https://gist.github.com/hhatto/7548246

Owner

hhatto commented Nov 19, 2013

in progress...

error output
https://gist.github.com/hhatto/7548246

@lepture

This comment has been minimized.

Show comment
Hide comment
@lepture

lepture Dec 20, 2013

Contributor

Any news?

Contributor

lepture commented Dec 20, 2013

Any news?

@Anomareh

This comment has been minimized.

Show comment
Hide comment
@Anomareh

Anomareh Jan 15, 2014

I'm looking to migrate my static site generator from misaka to hoedown however I have too many users on Mac. Has any progress been made on this issue?

I'm looking to migrate my static site generator from misaka to hoedown however I have too many users on Mac. Has any progress been made on this issue?

@swernerx

This comment has been minimized.

Show comment
Hide comment
@swernerx

swernerx Jan 31, 2014

Same issue here. I am trying to convert Jasy - the web tooling platform (https://github.com/sebastian-software/jasy) from Misaka to hoedown. There are a few different issues ranging from segmentation faults to wrong results. Maybe it's more related to the hoedown C-part (feels like memory access issues).

See output:
https://gist.github.com/wpbasti/8733533

Running the test suite it fails in different regions each time.

Same issue here. I am trying to convert Jasy - the web tooling platform (https://github.com/sebastian-software/jasy) from Misaka to hoedown. There are a few different issues ranging from segmentation faults to wrong results. Maybe it's more related to the hoedown C-part (feels like memory access issues).

See output:
https://gist.github.com/wpbasti/8733533

Running the test suite it fails in different regions each time.

@swernerx

This comment has been minimized.

Show comment
Hide comment
@swernerx

swernerx Jan 31, 2014

I've just updated the "inner" C-implementation of hoedown with the newest files from "master". This still does not help. I am unfortunately not so much a C-professional to figure this out. Any help would be appreciated!

I've just updated the "inner" C-implementation of hoedown with the newest files from "master". This still does not help. I am unfortunately not so much a C-professional to figure this out. Any help would be appreciated!

swernerx added a commit to sebastian-software/jasy that referenced this issue Jan 31, 2014

@philwo

This comment has been minimized.

Show comment
Hide comment
@philwo

philwo Feb 12, 2014

I encountered this bug today, too. I can reliably crash the Django devserver if I use python-hoedown in a view to convert Markdown to HTML. It usually happens under load and I also noticed corrupted memory (variables in my templates suddenly contained junk, then one more page reload crashed the devserver). Disabling threading in the devserver didn't help.

philwo commented Feb 12, 2014

I encountered this bug today, too. I can reliably crash the Django devserver if I use python-hoedown in a view to convert Markdown to HTML. It usually happens under load and I also noticed corrupted memory (variables in my templates suddenly contained junk, then one more page reload crashed the devserver). Disabling threading in the devserver didn't help.

@Anomareh Anomareh referenced this issue in hoedown/hoedown Apr 1, 2014

Closed

New Python binding. #68

@hhatto

This comment has been minimized.

Show comment
Hide comment
@hhatto

hhatto Oct 3, 2016

Owner

fix in version 0.2.2 ( 0cf78df )

Owner

hhatto commented Oct 3, 2016

fix in version 0.2.2 ( 0cf78df )

@hhatto hhatto closed this Oct 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment