Instiki / Markdown bug (another)

[Guillaume Marcais]

This time I have not yet found where in the input it chokes. But here
is the error:

Internal Server Error
/home/development/SOURCE/Ruby/instiki-0.8.1/app/models/../../libraries/
bluecloth.rb:341:in `gsub!': Stack overflow in regexp matcher: / ^ #
Start of line <(p|div|h[1-6]|blockquote|pre|table|dl|ol|ul|script) #
Start tag: \2 \b # word break (.*\n)*? # Any number of lines, minimal
match <\/\1> # Matching end tag [ ]* # trailing spaces (?=\n+|\Z) # End
of line or document /ix

Keep up the good work, I find Instiki & Markdown pretty nice.

Guillaume.

 

[David Heinemeier Hansson]

Keep up the good work, I find Instiki & Markdown pretty nice.

Thanks. I hope Granger comes back online some time soon. I submitted a
bug fix for something else a while back, but he hasn't responded yet.
I'm sure he's in a much better position to take care of these things
than I amn.

But I'll get graceful exception handling in shortly.
--
David Heinemeier Hansson,
http://www.instiki.org/ -- A No-Step-Three Wiki in Ruby
http://www.basecamphq.com/ -- Web-based Project Management
http://www.loudthinking.com/ -- Broadcasting Brain
http://www.nextangle.com/ -- Development & Consulting Services

 

[Michael Granger]

Thanks. I hope Granger comes back online some time soon. I submitted a
bug fix for something else a while back, but he hasn't responded yet.
I'm sure he's in a much better position to take care of these things
than I amn.

But I'll get graceful exception handling in shortly.

Ack! I didn't realize I hadn't replied to you. My apologies, sir.

I entered the bug you reported in the BlueCloth project tracker on
RubyForge
(http://rubyforge.org/tracker/index.php?
func=detail&aid=525&group_id=230&atid=951), and have since tested and
committed your fix. I will hopefully be releasing 0.0.3b today, which
includes your fix plus a few others.

As regards the stack overflow error, I don't know if that's something I
can fix, as it comes from re.c, not BlueCloth itself. I'll try to
reproduce it, but I'm not sure where to start without some idea of the
input that caused it and the environment under which it was run. It may
be that just setting the stack size to a greater value will fix the
problem (e.g.,
http://www.rubygarden.org/ruby?RubyOnMacintosh/FixStackSize), but I'm
not sure.

 

[Guillaume Marcais]

[gus@gusmac tmp]$ ulimit -a | grep stack
stack size (kbytes, -s) 8192

It already has a pretty large value...

Guillaume.

Le 29 avr. 04, à 11:48, Michael Granger a écrit :