Segmentation Fault with Markdown

[european bob]

Hi Jonathan,

On Sat, 2004-05-22 at 03:39, Jonathan Ploudre wrote:
> It's been a while since I've been on this list. I downloaded all the 
> archives and can't find a mention of other people having segmentation 
> faults. I'm running it on perl 5.6.0 on AIX. When I ran blosxom with 
> the perl -w command, it would crash only if Markdown 1.0b4 was enabled.
> 
> I got an error that said:
> 
> ======================
>   Use of uninitialized value in substitution (s///) at 
> /hw55/d57/tacmed/admin/blosxomplugins/Markdown line 222.
> ======================

That's not a segmentation fault. Did perl actually segfault? 

If it *did* segfault, the real problem is basically with your perl - a
segfault is always, always a bug in the program, and Markdown doesn't
count (it's interpreted, and doesn't play with memory pointers). It also
potentially sounds like it's tripping up on something strange in your
text - what were you processing?

> I just downloaded 1.0b5 and it seems to work. Odd, that, the line that 
> gives the error on b4 looks unchanged to me.

The above error message isn't referring to the actual bug, but the line
the bug appeared. "Use of uninitialised value" basically means that
there is a regex on one of the lines before that was supposed to capture
a variable, and it's success wasn't checked, or something similar.
Sounds like a bug that was fixed, really.

> ======================
> Malformed UTF-8 character at 
> /hw55/d57/tacmed/admin/blosxomplugins/Markdown line 1130.
> ======================
> 
> Anybody have ideas about whether that is a real error -- even though my 
> personal setup seems to work right now?

Looks real to me :o)

Sounds again like something in the input document isn't being liked. Are
you trying with a simple test document, or is this something more
complex?

--bob