On Sonntag 17 Februar 2008, Sergey M Plis wrote: > Yes. Thanks! I thought of the workaround right after I localized the > cause down to the example. It is just that the idea of legitimate > command sequence causing segfault makes me uncomfortable - so I > emailed. I mean, this should ideally be either documented (lol) or > some other workaround implemented so that no segfaults happen with > non-user written code.
The problem here is that OOF needs to hook into the forget/marker code. Perhaps I should use a way to chain those extensions together that can be tracked by this code, as well ;-). > Well, in any case, the workaround does its job. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
signature.asc
Description: This is a digitally signed message part.
