dlurk

Instant crash with regexp substitution with the following patch. I seem 

to remember crashing bugs with regexp, but I couldn't find them in the 

forum (via Google) or in my personal archive. I did a search of my 

entire drive for any name containing "regexp" - aside from the 4.6.2 

object and help, I found only 4.5.5's versions (not in 4.6.2 path) and 

cygwin's resources (also not in Max's path).

Max 4.6.2 on WinXP, all incremental updates applied. The postmortem 

Am I doing something wrong? I'll try the js version as a stopgap, but I 

wouldn't mind having the native object working.

Instant crash with regexp substitution with the following patch.  I seem 
to remember crashing bugs with regexp, but I couldn't find them in the 
forum (via Google) or in my personal archive.  I did a search of my 
entire drive for any name containing "regexp" - aside from the 4.6.2 
object and help, I found only 4.5.5's versions (not in 4.6.2 path) and 
cygwin's resources (also not in Max's path).

Max 4.6.2 on WinXP, all incremental updates applied.  The postmortem 
doesn't even kick in on this one.

Am I doing something wrong?  I'll try the js version as a stopgap, but I 
wouldn't mind having the native object working.

regexp-crash

No crash with v4.6 /OSX.4.8
But substitute does report nothing.
What result are you expecting with it?

I have tried a few different things. Originally I was just going for

So the expected output from "1 2 3" would be "3-1-2"

Everything I've tried with substitute *except* the help patch has 

crashed Max. I'm not really sure what the crucial difference is, unless 

the multiple backreferences are a problem.

I also don't know whether I just have some sort of systemic badness 

going on. I don't recall having problems with js before either, but I 

am having a strange one now (there's another thread open about it).

Philippe Gruchet wrote:
> No crash with v4.6 /OSX.4.8
> But substitute does report nothing.
> What result are you expecting with it?

I have tried a few different things.  Originally I was just going for

@re ([\d]+)[\s]+([\d]+)[\s]+([\d]+)
substitute %3-%1-%2

Everything I've tried with substitute *except* the help patch has 
crashed Max.  I'm not really sure what the crucial difference is, unless 
the multiple backreferences are a problem.

I also don't know whether I just have some sort of systemic badness 
going on.  I don't recall having problems with js before either, but I 
am having a strange one now (there's another thread open about it).

>> So the expected output from "1 2 3" would be "3-1-2"

> Sorry for the silly question but, why don't you just use sprintf? It's 

> made for string concatenation. Regexp is mainly designed for "searching".

Not silly, of course. This is a first step on the way to somewhere 

else... somewhere terribly boring, unfortunately. I'm not worried about 

it, as there are other avenues to PCRE goodness. But I was dismayed 

that it didn't work and took the current patch state down with it.

Emmanuel Jourdan wrote:
>> So the expected output from "1 2 3" would be "3-1-2"
>
> Sorry for the silly question but, why don't you just use sprintf? It's 
> made for string concatenation. Regexp is mainly designed for "searching".

Not silly, of course.  This is a first step on the way to somewhere 
else... somewhere terribly boring, unfortunately.  I'm not worried about 
it, as there are other avenues to PCRE goodness.  But I was dismayed 
that it didn't work and took the current patch state down with it.


I can confirm the problems, and will see if a fix can be easily made. 

>> What result are you expecting with it?

> I have tried a few different things. Originally I was just going for

> So the expected output from "1 2 3" would be "3-1-2"

> Everything I've tried with substitute *except* the help patch has 

> crashed Max. I'm not really sure what the crucial difference is, 

> unless the multiple backreferences are a problem.

> I also don't know whether I just have some sort of systemic badness 

> going on. I don't recall having problems with js before either, 

> but I am having a strange one now (there's another thread open 

I can confirm the problems, and will see if a fix can be easily made.  
No promises, though.

> Philippe Gruchet wrote:
>> No crash with v4.6 /OSX.4.8
>> But substitute does report nothing.
>> What result are you expecting with it?
>
> I have tried a few different things.  Originally I was just going for
>
> input: "int int int"
>
> @re ([\d]+)[\s]+([\d]+)[\s]+([\d]+)
> substitute %3-%1-%2
>
> So the expected output from "1 2 3" would be "3-1-2"
>
> Everything I've tried with substitute *except* the help patch has  
> crashed Max.  I'm not really sure what the crucial difference is,  
> unless the multiple backreferences are a problem.
>
> I also don't know whether I just have some sort of systemic badness  
> going on.  I don't recall having problems with js before either,  
> but I am having a strange one now (there's another thread open  
> about it).
>
> Thanks for checking this out!
>
> Jon


Thanks! It's not a showstopper, so no worries (for me anyway).

> I can confirm the problems, and will see if a fix can be easily made. No 

>> Everything I've tried with substitute *except* the help patch has 

>> crashed Max. I'm not really sure what the crucial difference is, 

>> unless the multiple backreferences are a problem.

Thanks!  It's not a showstopper, so no worries (for me anyway).

Jeremy Bernstein wrote:
> I can confirm the problems, and will see if a fix can be easily made. No 
> promises, though.
>
>> Everything I've tried with substitute *except* the help patch has 
>> crashed Max.  I'm not really sure what the crucial difference is, 
>> unless the multiple backreferences are a problem.


Just a followup -- thanks very much for your clear example. I found 

the problem and have fixed it. Should be released sometime soon.

> Max 4.6.2 on WinXP, all incremental updates applied. The 

> postmortem doesn't even kick in on this one.

Just a followup -- thanks very much for your clear example. I found  
the problem and have fixed it. Should be released sometime soon.

> Max 4.6.2 on WinXP, all incremental updates applied.  The  
> postmortem doesn't even kick in on this one.


regexp crash