1)Introduction: in the current Scrum Guide (July 2013) in page 11, the elements are listed which are included in Sprint Review: "... 3rd bullet point: The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;" ..."
2) Question: Why should it be discussed during Sprint Review? Is the Sprint Retrospective not the better place to handle these topic?
Illya is spot on. The Review should be focused on the Product. The Retrospective should address the process and behavior of the Scrum Team and its interfaces. In their own distinct ways, both are opportunities to inspect and adapt the value stream.
However, I can sympathise with Mehdi's concern. The problems that are identified in a Sprint Review are often human ones. The important thing is not to solutionize behavioral or process problems in the Review, but rather to identify facts. These are the facts that certain problems happened and that they were addressed in a certain way. Such objective findings can then be used to inform the Sprint Retrospective, and dysfunctions in process can be remedied.