David,
With the new Air dialog box, I'm running into a segfault. What I do
to trigger the crash is first bringe up the Air dialog box, then I
examine the data and decide I don't want to change anything, then I
click ok.
The back trace lists a bunch of internal PUI calls and then dies in
Curtis L. Olson writes:
With the new Air dialog box, I'm running into a segfault. What I do
to trigger the crash is first bringe up the Air dialog box, then I
examine the data and decide I don't want to change anything, then I
click ok.
The back trace lists a bunch of internal PUI
Michael Basler writes:
With the new Air dialog box, I'm running into a segfault. What I do
to trigger the crash is first bringe up the Air dialog box, then I
examine the data and decide I don't want to change anything, then I
click ok.
...
Seems to double my observation.
From: Michael Basler [EMAIL PROTECTED]
Curt,
With the new Air dialog box, I'm running into a segfault. What I do
to trigger the crash is first bringe up the Air dialog box, then I
examine the data and decide I don't want to change anything, then I
click ok.
...
Seems to double my
Do the
LatLonFormatToggle
or the
AutoPilotAdjuster
Work for anybody ???
FWIW I added some printfs() and it does not appear if either
of their 'launchers' is ever fired()
Note:
The AddWayPoint and PopWayPoint 'launchers' do print
their debug messages
Norman
extern void AddWayPoint (puObject
David,
What versions of plib and G++ are you using?
PLIB CVS as of today. GCC 2.95.
Regards, Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
___
Flightgear-devel
David Megginson writes:
There was a typo bindings instead of binding -- it's fixed now.
It would be nice if had a 'lint' like XML checker for all of the 'properties'
Anyone know of an OpenSource alternative to XMLSpy
Norman
___
Norman Vine writes:
It would be nice if had a 'lint' like XML checker for all of the
'properties'
We get an error if the XML document is not well-formed, but not if
there is an unrecognized property. There are lots of good reasons for
keeping it that way.
Anyone know of an OpenSource
The new XML-configured menubar is now the default for FlightGear;
configure --with-old-menubar to get the old one (which I'll keep
around for now, until we're sure the new one is working OK).
Please, everyone, give the new menubar a spin, and take a look at
$FG_ROOT/gui/menubar.xml and
David Megginson writes:
The new XML-configured menubar is now the default for FlightGear;
configure --with-old-menubar to get the old one (which I'll keep
around for now, until we're sure the new one is working OK).
Please, everyone, give the new menubar a spin, and take a look at
Curtis L. Olson writes:
One thing I'd like to have is a --disable-menu/--enable-menu option so
that we can have the menu start off by default if we want.
Yes, I need to reinstate show/hide menu -- thanks for the reminder.
All the best,
David
--
David Megginson, [EMAIL PROTECTED],
Michael Basler writes:
One issue: When I make a selection from the Weather menu the dialog box
opens as it should. However, after only pressing either OK or Cancel the
simulator silently dies with a stackdump as follows:
_
token = OBJECT_BASE name =
David,
That looks like it's just program output. Can you get a proper
backtrace in gdb or some other debugger?
This would imply me knowing how to use it. I am not a programmer, just an
ordinary poor physicist...
I analyzed a core file with gdb once. However, FG doesn't dump a core file
Typically you run fgfs from within gdb.
Something like
bash$ gdb fgfs
gdb run --fgfs-option1 --fgfs-option2
Then when you get a crash you can type:
gdb where
To get a back trace.
Regards,
Curt.
Michael Basler writes:
David,
That looks like it's just program output. Can you get a
Curt, David
I already messed a bit around with gdb, but it always died. Mean issue was I
set --fg_root= instead of fg-root= :-(((
It now does run. However, after selecting the button in question, flightgear
never dies completely. Instead, it hangs infinitely. I had to kill it
manually.
The
Michael Basler writes:
That looks like it's just program output. Can you get a proper
backtrace in gdb or some other debugger?
This would imply me knowing how to use it. I am not a programmer, just an
ordinary poor physicist...
I analyzed a core file with gdb once. However, FG doesn't
On Sat, 18 Jan 2003 12:39:32 -0500
David Megginson [EMAIL PROTECTED] wrote:
The new XML-configured menubar is now the default for FlightGear;
configure --with-old-menubar to get the old one (which I'll keep
around for now, until we're sure the new one is working OK).
Please, everyone, give
Bernie Bright writes:
On Sat, 18 Jan 2003 12:39:32 -0500
David Megginson [EMAIL PROTECTED] wrote:
The new XML-configured menubar is now the default for FlightGear;
configure --with-old-menubar to get the old one (which I'll keep
around for now, until we're sure the new one is working
David,
I'm not sure your thinking on this, but the Reset option has
disappeared. That's kind of nice if you want to do a complete reset
of everything.
Regards,
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL
19 matches
Mail list logo
