Low-temperature evolution of the Morondava rift basin shoulder in western Madagascar: An apatite fission track study

[1] The evolution of the rift shoulder and the sedimentary sequence of the Morondava basin in western Madagascar was mainly influenced by a Permo-Triassic continental failed rift (Karroo rift), and the early Jurassic separation of Madagascar from Africa. Karroo deposits are restricted to a narrow corridor along the basement-basin contact and parts of this contact feature a steep escarpment. Here, apatite fission track (AFT) analysis of a series of both basement and sediment samples across the escarpment reveals the low-temperature evolution of the exhuming Precambrian basement in the rift basin shoulder and the associated thermal evolution of the sedimentary succession. Seven basement and four Karroo sediment samples yield apparent AFT ages between ∼330 and ∼215 Ma and ∼260 and ∼95 Ma, respectively. Partially annealed fission tracks and thermal modeling indicate post-depositional thermal overprinting of both basement and Karroo sediment. Rocks presently exposed in the rift shoulder indicate temperatures of >60°C associated with this reheating whereby the westernmost sample in the sedimentary plain experienced almost complete resetting of the detrital apatite grains at temperatures of about ∼90–100°C. The younging of AFT ages westward indicates activity of faults, re-activating inherited Precambrian structures during Karroo sedimentation. Furthermore, our data suggest onset of final cooling/exhumation linked to (1) the end of Madagascar's drift southward relative to Africa during the Early Cretaceous, (2) activity of the Marion hot spot and associated Late Cretaceous break-up between Madagascar and India, and (3) the collision of India with Eurasia and subsequent re-organization of spreading systems in the Indian Ocean.

Practical Object-Oriented Back-in-Time Debugging

Back-in-time debuggers are extremely useful tools for identifying the causes of bugs, as they allow us to inspect the past states of objects no longer present in the current execution stack. Unfortunately the "omniscient" approaches that try to remember all previous states are impractical because they either consume too much space or they are far too slow. Several approaches rely on heuristics to limit these penalties, but they ultimately end up throwing out too much relevant information. In this paper we propose a practical approach to back-in-time debugging that attempts to keep track of only the relevant past data. In contrast to other approaches, we keep object history information together with the regular objects in the application memory. Although seemingly counter-intuitive, this approach has the effect that past data that is not reachable from current application objects (and hence, no longer relevant) is automatically garbage collected. In this paper we describe the technical details of our approach, and we present benchmarks that demonstrate that memory consumption stays within practical bounds. Furthermore since our approach works at the virtual machine level, the performance penalty is significantly better than with other approaches.