On Sat, 10 Apr 2004 18:39:24 +0200, Jorge Van Hemelryck
<[EMAIL PROTECTED]> wrote:
>On Fri, 9 Apr 2004 10:11:27 +0100
>Jonathan Richards <[EMAIL PROTECTED]> wrote:
>> Yesterday, you wrote '... we can't distribute
>> ... even the symbol definitions' which I find intriguing; when I last had
>>
Durk Talsma writes:
>
> That's what I would guess. B.t.w, I've found a way to consistently replicate
> the crash, using a relatively short route (about 25 minutes). This route
> requires tile e000n50, as I'm taking off from Amsterdam Schiphol, and
> "crashing" the program at Den Helder Airpor
I just tried this fix, but I'm afraid that this didn't solve the problem. I
still got the crash. What's more worriesome is that it appears that
FlightGear-0.9.4 already has this bug. I just compiled and tested the release
version and, again, got the abort at 10 nm east of EHKD*. So I'm afraid th
On Sat, 10 Apr 2004 01:46:21 +0100
Rick Ansell <[EMAIL PROTECTED]> wrote:
> On Fri, 9 Apr 2004 13:52:50 +0200, Arnt Karlsen <[EMAIL PROTECTED]>
> wrote:
>
> >..inline with this, you oughtta be possible to rip out the secret
> >military parameters, put in new ones from, say, a Taylor Cub,
> >and
On Fri, 9 Apr 2004 10:11:27 +0100
Jonathan Richards <[EMAIL PROTECTED]> wrote:
> I've been reading this thread with interest. You'll tell me if I'm wrong,
> JvH, but I believe the situation is that the HUD code (i) contains
> information which is proprietary ("industrial property") and (ii) att
On Fri, 9 Apr 2004 13:45:16 +0200
Arnt Karlsen <[EMAIL PROTECTED]> wrote:
> ...which forces the obligation on your part to provide the source to
> whomever you provides your modification to. And, doing contract
> work for them on their HW, you probably have complied to the GPL
> here. ;-)
The
I found something that might be a candidate for the overflow. Around
this timeframe, some sprintf("%f") code got added to the atis handler.
The problem is, printf() can generate almost unbounded output for very
large values* and the buffer is only 10 bytes long.
* Try this: int main() { prin
On Saturday 10 April 2004 14:18, Jon Berndt wrote:
> > Okay, I can confirm that the program crash also happens with a JSBSim
> > aircraft. I used the the A320 (sorry David, the 737 autopilot
> > appears not to
> > support waypoint following, so I couldn't use it, for testing purposes).
> > Since t
> Okay, I can confirm that the program crash also happens with a JSBSim
> aircraft. I used the the A320 (sorry David, the 737 autopilot
> appears not to
> support waypoint following, so I couldn't use it, for testing purposes).
> Since threading doesn't appear to make a difference, I enabled i
Okay, I can confirm that the program crash also happens with a JSBSim
aircraft. I used the the A320 (sorry David, the 737 autopilot appears not to
support waypoint following, so I couldn't use it, for testing purposes).
Since threading doesn't appear to make a difference, I enabled it again for
On 8 Apr 2004 at 17:57, Carlos Renato wrote:
> Hi,
>
> I am trying to assemble a cockpit with simulated instruments, I checked the
> previus messages and I found the procedures to use some different joysticks
> but there were no information for instrumentation, does someone developed
> the gauge
11 matches
Mail list logo
