I ran the null pointer dereference checker over 2.4.3 and it found thefollowing 15 potential errors. As usual, the context given with eachreport may be misleading so you'll probably need to inspect thesource. The checker tries to help by printing the function it thinksis returning NULL.

Also, I've run the checker over 2.2.19, and there were a bunch ofissues but they would require some time and effort to inspect. Someof them are the same as issues reported for 2.4.x. Would it be usefulto report these?