Custom Query (95 matches)

This quirk has been in Aven since whenever. I suspect that most people, like me, have just ignored it since it doesn't impede use of the software; it's merely a cosmetic defect.

As an example, the depth scale on the survey I'm currently looking at is labelled starting at -1.14e-10mm. This is plainly spurious... we try hard to maintain a reasonable degree of survey precision, but I think that the nearest metre should usually be acceptable on Aven's depth scale!

These seem to print reversed so they don't fit with the underground legs (Julian said this is something to do with the difference between what Survex and what the printer takes as the page origin).

Running aven on a 64bit linux (fedora 16) laptop only displays an error message "Bug in program detected! Please report this to the authors" and then exits. Running aven from the command line displays:

[james@jumbo ~]$ aven
Bad memory access
[james@jumbo ~]$

Running aven through GDB (with no debugging symbols) gives

(gdb) file /usr/bin/aven
Reading symbols from /usr/bin/aven...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/aven /usr/bin/aven
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 11340.
Detaching after fork from child process 11341.
Detaching after fork from child process 11342.

Program received signal SIGSEGV, Segmentation fault.
0x0000003d6e653136 in glClearColor () from /usr/lib64/libGL.so.1

Any ideas? version 1.2.2 was working fine ...