Hi there!
Thomas Förster wrote:
> Am Dienstag 03 Juli 2007 10:28 schrieb Vivian Meazza:
>> Of course code breakage happens. But in an ideal world, it shouldn't get
>> into cvs.
>
> In an ideal world we had automated unit test that cover everything... Welcome
> to reality :-P
In an ideal world
Am Dienstag 03 Juli 2007 10:31 schrieb Martin Spott:
> > Perhaps you recall this thread: "C++ code beautifier /
> > Codingstandardsproposal"
> >
> > Seems to me that we are just revisiting these issues.
>
> I can't remember having read a proposal that found general consensus in
> the mentioned thre
Am Dienstag 03 Juli 2007 10:28 schrieb Vivian Meazza:
> Of course code breakage happens. But in an ideal world, it shouldn't get
> into cvs.
In an ideal world we had automated unit test that cover everything... Welcome
to reality :-P
> It makes us all look unprofessional.
Not more than not ha
Vivian,
"Vivian Meazza" wrote:
> Of course code breakage happens. But in an ideal world, it shouldn't get
> into cvs. It makes us all look unprofessional. Proper peer review can help
> prevent this. At least it gives others, perhaps more expert than us a chance
> to spot things that we have misse
"Vivian Meazza" wrote:
> Martin Spott
> > Well, before this turns into mutual instructions on how to
> > translate Latin, we'd better return to a more common
> > language. We still don't know the answer to your question
> > "What were we saying about ", do we ?
> >
> Perhaps you recall th
Durk Talsma
> Sent: 03 July 2007 06:36
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] crash in AI traffic
>
>
> On Tuesday 03 July 2007 00:20, Vivian Meazza wrote:
>
> > > > > > > "Vivian Meazza" wrote:
> >
Am Dienstag 03 Juli 2007 08:30 schrieb Durk Talsma:
> The most significant exception (no pun indented) :-)
The context of a message also depends on the messenger :-)
> to this rule seems to
> be the one related to the routing algorithm. It seems like the new
> algorithm is pickier than my old o
On Monday 02 July 2007 10:05, Melchior FRANZ wrote:
> Yeah. It's also not only the Traffic Manager. FlightGear is full
> of exit()s, when there should really be one single exit() at most,
> and that would be in bootstrap.cxx. When the project was started,
> gcc wasn't what it is now. I think templa
On Tuesday 03 July 2007 00:20, Vivian Meazza wrote:
> > > > > > "Vivian Meazza" wrote:
> > > > > > > What were we saying about incompletely tested and poorly
> > > > > >
> > > > > > ^^
> > > > > >
[Lot's a latin skipped for clarity]
>
> Perhaps you recall this thread: "C++ code beaut
Martin Spott
> Sent: 02 July 2007 22:45
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] crash in AI traffic
>
>
> "Vivian Meazza" wrote:
> > Martin Spott
> > > Sent: 02 July 2007 16:32
> > > "Vivian Mea
"Vivian Meazza" wrote:
> Martin Spott
> > Sent: 02 July 2007 16:32
> > "Vivian Meazza" wrote:
> > > Martin Spott
> > > > "Vivian Meazza" wrote:
> >
> > > > > What were we saying about incompletely tested and poorly
> > > > ^^
> > > > > reviewed code getting into cvs ... ?
> > > >
> >
Martin Spott
> Sent: 02 July 2007 16:32
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] crash in AI traffic
>
>
> "Vivian Meazza" wrote:
> > Martin Spott
> > > "Vivian Meazza" wrote:
>
> >
On Monday 02 July 2007 13:25, Vivian Meazza wrote:
> I am one of those developers who have the traffic manager turned off. I
> have taken the trouble sometime ago to inform Durk directly, so he is well
> aware of this bug. Along with the one which causes AITankers to move at
> warp speed factor 2.
"Vivian Meazza" wrote:
> Martin Spott
> > "Vivian Meazza" wrote:
> > > What were we saying about incompletely tested and poorly
> > ^^
> > > reviewed code getting into cvs ... ?
> >
> > -> Plural majestatis ?
> Haud. Ego relatum ut an mane sermo.
Qui participavit in conclusio illa
Martin Spott
> Sent: 02 July 2007 15:42
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] crash in AI traffic
>
>
> "Vivian Meazza" wrote:
>
> > What were we saying about incompletely tested and poorly
> reviewed co
* Melchior FRANZ -- Monday 02 July 2007:
> I would definitely not ignore a message from the traffic manager:
>
> Traffic Manager problem in src/Traffic/TrafficMgr.cxx, line 341:
> routing problem in EHAM data -- no endpoint found
OK, here's the first addition: I've just added a macro SG_ORIGIN
"Vivian Meazza" wrote:
> What were we saying about incompletely tested and poorly reviewed code
^^
> getting into cvs ... ?
-> Plural majestatis ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
-
On 7/2/07, Durk Talsma <[EMAIL PROTECTED]> wrote:
> I agree that it can be very frustrating to have a flightgear session cancelled
> due to an exit, and in a released version, this should be avoided. However,
> the flip side is that if we continue to "gracefully recover", its going to be
> a lot to
Martin Spott wrote
> Sent: 02 July 2007 09:25
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] crash in AI traffic
>
>
> Melchior FRANZ wrote:
>
> > Several people (mostly developers) on IRC have stated that
> they have
> > th
> Thoughts, ideas, objections?
Though the property system is probably nice, why not just raise an exception +
a catch all error handler. In release code this probably just logs a warning,
whereas in debug/development code it exits (could be a commandline option).
This works for all subsystems a
Melchior FRANZ wrote:
> Several people (mostly developers) on IRC have stated that they have
> the traffic manager turned off because [...]
If you're really that serious about it, then you might start to help
getting the thing into better shape by asking these people to report
properly on this ve
* Melchior FRANZ -- Monday 02 July 2007:
> Sure, a property that turns every serious exception into a segfault
> couldn't hurt. A segfault, not an abort()!
Uh, I know: An abort() *makes* a coredump. I meant an exit(). :-)
m.
--
* Durk Talsma -- Monday 02 July 2007:
> I will look into that. FWIW, most of the exit()' s in the code were placed
> there during the early stages of development, and anyone of those remaining
> is in a spot where the probability of an error has become extremely small Or
> just nobody is reporti
On Monday 02 July 2007 08:44, Durk Talsma wrote:
> Hi Melchior,
>
> On Sunday 01 July 2007 15:47, Melchior FRANZ wrote:
> > I appreciate your work on the Traffic Manager, but ...
> >
> > * Durk Talsma -- Sunday 01 July 2007:
> FWIW, I believe the default setting of this property should be "true" i
Hi Melchior,
On Sunday 01 July 2007 15:47, Melchior FRANZ wrote:
> I appreciate your work on the Traffic Manager, but ...
>
> * Durk Talsma -- Sunday 01 July 2007:
> > The message is related to a routing problem in the AI system,
> > which actually causes a controlled exit from FlightGear.
>
> Ple
I appreciate your work on the Traffic Manager, but ...
* Durk Talsma -- Sunday 01 July 2007:
> The message is related to a routing problem in the AI system,
> which actually causes a controlled exit from FlightGear.
Please remove the "controlled exit". There's no reason why a
user flying along s
On Sunday 01 July 2007 12:31, alexis bory wrote:
>
> "Failed to find route from waypoint 8 to 154 at KSAN"
>
Hi Alexis,
Like Thomas explained, this is unrelated to the crash reported earlier. The
message is related to a routing problem in the AI system, which actually
causes a controlled ex
Am Sonntag 01 Juli 2007 12:31 schrieb alexis bory:
> I think this crash is related to the above:
>
> "Failed to find route from waypoint 8 to 154 at KSAN"
>
> whithout any other message in the console. FG just quits.
No, these seem to be unrelated. The latter happens if the route finding
algo
Durk Talsma a écrit :
> On Tuesday 26 June 2007 03:09, Csaba Halász wrote:
> > Hi!
> >
> > Helijah has run into a crash. Gdb backtrace here:
> > http://pastebin.ca/589461 (no debug symbols unfortunately)
> >
> > Looks like the "next" waypoint is null. As a quick and dirty fix I
> > came up with th
On 6/26/07, Durk Talsma <[EMAIL PROTECTED]> wrote:
> On Tuesday 26 June 2007 03:09, Csaba Halász wrote:
> > Hi!
> >
> > Helijah has run into a crash. Gdb backtrace here:
> > http://pastebin.ca/589461 (no debug symbols unfortunately)
>
> Thanks for reporting. I'll have a look. Can you give me some s
On Tuesday 26 June 2007 03:09, Csaba Halász wrote:
> Hi!
>
> Helijah has run into a crash. Gdb backtrace here:
> http://pastebin.ca/589461 (no debug symbols unfortunately)
>
> Looks like the "next" waypoint is null.
> As a quick and dirty fix I came up with this:
>
> Index: src/AIModel/AIAircraft.c
Hi!
Helijah has run into a crash. Gdb backtrace here:
http://pastebin.ca/589461 (no debug symbols unfortunately)
Looks like the "next" waypoint is null.
As a quick and dirty fix I came up with this:
Index: src/AIModel/AIAircraft.cxx
===
32 matches
Mail list logo
