Re: Phix segfault when wildcard_match file between 1.5 and 2 million lines
- Posted by lib9 3 months ago
- 643 views
That's nice. Reminds me of a brilliant phone prank I once heard: guy gets a call from a satelite dish salesman, so pretends to be a detective at a murder scene, with a proper deep southern drawl:
(after warning him not to hang up, asking him how he knows the victim, and generally scaring the pants off him and not letting him get a word in edgeways)
Detective: Whe're you now?
Terrified Salesman: At work.
Detective: You tryin to be funny? What would I need to put on the OUTSIDE of an envelope to get a letter t'yr sorry ass?
I'm not native english speaker and I miss the message you're trying to convey to me. Direct meaning is preferable, for me.
Let's try a different tack. Does it still crash if you remove object txt = read_lines(t_file)?
Does wildcard_match("*some string*",line) ==> match("some string",line) (ditto other) work?
How about (undoing that then, and) if you remove buffer = append(buffer, line)?
If you then add ?i after incrementing it, does it always crash at the same place?
Assuming it does, on line NNNNNN, what does if i>=NNNNNN then ?line end if show?
And is the ex.err that generates small enough to be pasted here?
1. If I remove object txt = read_lines(t_file):
It doesn't segfault.
I tried two methods of reading the input file and seem to have forgot that line.
2. #match("some string",line) (not using asterisks), but with the object txt = read_lines(t_file)
Continues to sefault.
3. Like 2., but without object txt = read_lines(t_file)
Runs fine.
4. Remove buffer = append(buffer, line), keep the rest as in my code, so with object txt = read_lines(t_file).
Runs fine.
5. ?i
No, it stops at different lines, like line number 1993109, 1992407, 1992925.
6. It didn't generate any ex.err file.
Thanks.
