Question

I have a Delphi 5-based application using madExcept 3.0m. It appearantly freezes due to madExcept, a product whose quality I admire and thus don't usually blame for anything.

Here's the code:

  AddLogEntry('ME_Settings');
  try
    AddLogEntry('ME_Settings2');
    with MESettings do begin                     // madExcept-Einstellungen
      AddLogEntry('FrozenMsg');
      sOldFrozenMsg := FrozenMsg;
      AddLogEntry('Meldung vorbereiten');
      FrozenMsg := AnsiString(_('Das Öffnen der Datenbank dauert ungewöhnlich lang.'));
      AddLogEntry('Remote?');
      [...]
    end;
  finally
    [...]
  end;

It doesn't throw any exception, it just seems to freeze upon reading FrozenMsg:
(source: quodata.de)

It doesn't happen on any of my computers, but does at the customer computer. How can madExcept's MESettings cause such a behaviour. How should I debug this?

Was it helpful?

Solution

We have now deployed a regular update using a regular (and very same) madExcept 3.0m to the customer. It worked. They replaced the computer due to other problems, so I am quite confident that the problem was with the specific computer and nothing needs to be fixed in madExcept or our products.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top