On 11 Dec 2009, at 19:32, Csaba Halász wrote:
Also, the whole positioned code seems to be ignorant of the fact that
buckets don't have the same size. Staying with the spatialGetClosest,
it assumes it can just use NxN boxes when in fact a different row
(latitude) could have half or double the
Hi!
Alex was kind enough to give me shell access to his machine so I think
I have this beast figured out.
1) The immediate cause of the crash is due to
DistanceOrdering::operator() accessing an invalid pointer
2) The reason for that is std::sort indexing before the array (man, I
hate templates!)
On Fri, Dec 11, 2009 at 4:13 PM, Csaba Halász csaba.hal...@gmail.com wrote:
are not guaranteed to be the nearest ones. Also, I am not entirely
sure that the current cutoff distance checking is sufficient. Let's
suppose a coordinate system centered on the bucket containing the ref
point at the
Dont know if this helps.
but I compiled SG and FG with and without the CXXFLAGS.
It only crashes when CXXFLAGS are NOT on FG, which seems to indicate a
FG problem.
Also noted is that the crash seems to happen 9 times out of ten to the
west of prime, no matter how its approached.
Is there
Just catching up on the thread (been away).
I compiled SG and FG with CXXFLAGS=-g -O0 and its fantastic. For the
first time I can fly around London airspace without a segfault. (never
tried the dist packages so cant report on that).
As far as finding the bug, I tried a lot of areas to try and
On Sun, 01 Nov 2009 20:35:01 +
James Turner zakal...@mac.com wrote:
On 1 Nov 2009, at 19:24, Alex D-HUND wrote:
At the moment I am out of ideas on what to try out next, I am open
for suggestions.
I keep forgetting to dig into this issue, apologies for that. I'll add
it to
On Mon, 26 Oct 2009 21:54:08 +0100
Alex D-HUND f...@beggabaur.de wrote:
In the meantime I have installed valgrind and I am doing my first steps with
it. A first trial run turned out to be very good, I already saw the scenery
ten minutes after starting it. ;-)
Ahoy Guys,
beside that
On 1 Nov 2009, at 19:24, Alex D-HUND wrote:
At the moment I am out of ideas on what to try out next, I am open
for suggestions.
I keep forgetting to dig into this issue, apologies for that. I'll add
it to my ToDo list now, and take a look this week.
Regards,
James
James Turner wrote:
On 1 Nov 2009, at 19:24, Alex D-HUND wrote:
At the moment I am out of ideas on what to try out next, I am open
for suggestions.
I keep forgetting to dig into this issue, apologies for that. I'll add
it to my ToDo list now, and take a look this week.
Recently I
On 25 Oct 2009, at 21:24, Alex DaHUND wrote:
Now I was able to make some backtraces (http://nopaste.org/p/
aPZTtaYYX). Jester pointed out, that this could be a problem of the
optimisation during the build process and advised me to configure SG
and FG with option CXXFLAGS=-g -O0. He was
On 26 Oct 2009, at 09:14, James Turner wrote:
If it's an optimisation-related bug, tracing it is going to be pretty
awful. That said, the crash seems rather widespread for a straight
compiler issue. I'm also surprised that a compiler bug would change
frequency based on compile options.
On Mon, Oct 26, 2009 at 10:40 AM, James Turner zakal...@mac.com wrote:
Incidentally, -O0 often implies that all values are initialised to
zero, which could by why it fixes the problem. Valgrind should catch
such an issue, if anyone is able to actually fly FG while running
under VG - on Mac
On Mon, Oct 26, 2009 at 4:14 AM, James Turner zakal...@mac.com wrote:
If it's an optimisation-related bug, tracing it is going to be pretty
awful. That said, the crash seems rather widespread for a straight
compiler issue. I'm also surprised that a compiler bug would change
frequency based on
On 26 Oct 2009, at 17:15, Curtis Olson wrote:
It would be interesting to see what the back trace is with
optimization turned on.
Absolutely - unfortunately, for whatever reason, none of the people
who can easily generate a backtrace, have been able to reproduce the
crash - I've tried,
It would be interesting to see what the back trace is with
optimization turned on.
Absolutely - unfortunately, for whatever reason, none of the people
who can easily generate a backtrace, have been able to reproduce the
crash - I've tried, Jester has tried, and assorted others on
Hi Alex,
Ok, based on the backtrace, this would implicate something in the gps or
perhaps FGPositioned code trying to do some sort of spatial sort?
Regards,
Curt.
On Mon, Oct 26, 2009 at 3:54 PM, Alex D-HUND wrote:
It would be interesting to see what the back trace is with
optimization
Hi Pete,
I can confirm this bug. Problem with it, it does not happen all the time. I
encountered it while preparing for the 'Euro Zone Event', taking off at EGLL
heading to EHAM with the ufo to prefetch scenery. And it was even possible to
reproduce the crash. So, the other day I asked on IRC
On 14 Sep 2009, at 00:23, Pete Morgan wrote:
Flying the East to West eg from EGLC London City to EGLL Heathrow
crashes in a similar fashion.
That's weird, I flew from EGLL to EGLC just the other day, and it
worked fine.
I'll try the route, and aircraft you suggested, in the next couple of
18 matches
Mail list logo
