Stacho

The error that I experienced was not caused by the change from 5.3.9 to 5.3.10 but rather I suspect a recent change that I made in my dataset.

So most likely my fault in not identifying the cause correctly.

I get the same error for particular thconfig files and selections regardless of the therion version, and other thconfig files are OK in both versions.

The debug version you sent me gives this;

…

LEG: -@de [1999] (from DE23.12@de [1993])

LEG: -@de [1998] (from DE23.12@de [1993])

LEG: -@de [1997] (from DE23.12@de [1993])

LEG: -@de [1996] (from DE23.12@de [1993])

LEG: -@de [1995] (from DE23.12@de [1993])

LEG: -@de [1994] (from DE23.12@de [1993])

LEG: -@de [1992] (from DE23.11@de [1980])

LEG: -@de [1991] (from DE23.11@de [1980])

LEG: -@de [1990] (from DE23.11@de [1980])

LEG: -@de [1989] (from DE23.11@de [1980])

LEG: -@de [1988] (from DE23.11@de [1980])

LEG: -@de [1987] (from DE23.11@de [1980])

LEG: -@de [1986] (from DE23.11@de [1980])

LEG: -@de [1985] (from DE23.11@de [1980])

LEG: -@de [1984] (from DE23.11@de [1980])

LEG: -@de [1983] (from DE23.11@de [1980])

LEG: -@de [1982] (from DE23.11@de [1980])

LEG: -@de [1981] (from DE23.11@de [1980])

LEG: -@de [1979] (from DE23.10@de [1967])

D:\Program Files\Therion\therion.exe: error -- (thdb1d.cxx:2290): a software BUG is present (thdb1d.cxx:2290)

writing xtherion file ... done

and an inspection of a diff of my last data commit gives me;

…

centreline

explo-date 2012.01.22

explo-team "Bruce Mutton"

explo-date 2012.06.24

explo-team "Michael Brewer"

date 2012 #date needed to suppress 'undated survey declination' error

data nosurvey from to

DE23.10@de dm30.15@dm #unsurveyed connection Bermuda Triangle Spiders Lair

DJ27.5@dj dm30.15@dm #unsurveyed new main route Hobbit Hole Spiders Lair

endcentreline

Intriguingly this centerline does not give an error when it is processed at this cave level, but it does when it is processed at a higher level as part of a multi-cave compilation.  So it is inconsistent in the way it triggers a crash.

My initial guess is that there is something about my (almost) first usage of ‘nosurvey’ that Therion does not like.  2x nosurveys to the same station perhaps?

My initial trials suggest that commenting out the centerline above fixes the problem.

Any comments on whether my usage of nosurvey ‘breaks any rules’?

Ie Should it be considered a bug in my data file or a Therion bug?  (I guess at least the error should be trapped more gracefully).

Bruce

---

From: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] On Behalf Of Stacho Mudrak
Sent: Monday, 13 August 2012 9:41 p.m.
To: List for Therion users
Subject: Re: [Therion] OOPS: version 5.3.10

I am really sorry.

But unless you can extract a dataset, that causes the problem, I am not able to fix it :(

I will diff thdb1d.cxx changes and see, where potentially error can be, but some dataset, that causes this problem would help a lot. All my datasets seems to work fine.

S.