Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a Delphi application running on a terminal server that keeps generating dump files. For the same PID, it keeps creating dump files with an interval of around 1 second until the process is killed manually. Another weird thing is the name of the dump files:

±_minidump_default_pid_7916_tid_x6590_2012_6_18_13_48_40.dmp
÷_minidump_default_pid_7916_tid_x6590_2012_6_18_13_48_42.dmp
k_minidump_default_pid_7916_tid_x6590_2012_6_18_13_48_39.dmp
Ô_minidump_default_pid_7916_tid_x6590_2012_6_18_13_48_41.dmp
Ž_minidump_default_pid_7916_tid_x6590_2012_6_18_13_48_40.dmp

The dump files aren't telling us much and we would like to have a suggestion where we should start looking.

share|improve this question

The problem appeared to be in a component we used to communicate with Oracle. A new version of this component solved the issue.

It looked like the following scenario occurred:

  • An exception occurred;
  • The component tries to perform an action with Oracle;
  • Oracle triggered a minidump;
  • The component retried.

UPDATE:

Apparently this issue is caused by a faulty Oracle client. Updating to the latest version of the Oracle client fixed this issue for us.

share|improve this answer
    
Pieter, I'm trying to solve the same problem here. Are you using DevArt components? That's what we use here. – Rafael Piccolo Aug 13 '12 at 18:05
    
No; it's an Allround Automations component (Direct Oracle access). – Pieter van Ginkel Aug 14 '12 at 8:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .