Martin Fowler wrote about the Call Super smell. This occurs when you are allowed to override a method in a parent class, but you must (as opposed to can) call the parent implementation in your method.
As Martin says, this is a code smell. Why? Because it’s easy to forget, and if you forget it, you get a failure that may be hard to diagnose.
The right thing to do, of course, is to use the Template Method pattern. This allows you to provide “hooks” for subclasses to override. Of course, these hooks can then become smells in their own right if the subclass tree proliferates.
One of the best examples in this is in JUnit… but not in JUnit itself. JUnit uses the Template Method pattern by providing setUp() and tearDown() methods, to be run before and after test execution. Now, there are many extensions to JUnit, and they typically override setUp() and tearDown(). If subclasses want their own setUp() and tearDown() code, they have to… call super! (I remember that StrutsTestCase was particularly bad for this).
This regularly gets mention as a flaw in JUnit. Well, it’s not. Yes, there are better ways to identify setUp and tearDown code, such as the annotation-based approach used in NUnit, TestNG, and the upcoming JUnit 4.0, but there isn’t anything fundamentally wrong with the template method appraoch. The problem was that the extension designers took the easy way out and forced their children to call super instead of taking a bit of time to avoid this (for example, by overriding runBare() to put in pre- and post-test hooks of their own). Martin describes this exact approach in his own entry.
(Another approach that the extension authors could have done is made their functionality available as a Decorator. JUnit has decent decorator support, though constructing decorated tests is mildly annoying)
In short, call super is a problem when using inheritance to provide aggregation. You can avoid this by creating template methods, but in deep inheritance chains (which are their own code smell), these template methods themselves become problems.