On Wed, Dec 2, 2009 at 12:57 AM, Tim Moore wrote:
Just to be clear, are you running with
CullThreadPerCameraDrawThreadPerContext,
or what? How many of each?
Hi Tim,
I was running with AutomaticSelection and only had a single display enabled:
I've been observer quite frequent segfaults in the most recent version of
FlightGear. I've started running under gdb and so far the trend seems to be
that the crash is inside the pui code and as a result of clicking ok or
cancel on a dialog box. Here's an example backtrace (the build is without
On 1 Dec 2009, at 16:59, Curtis Olson wrote:
I've been observer quite frequent segfaults in the most recent version of
FlightGear. I've started running under gdb and so far the trend seems to be
that the crash is inside the pui code and as a result of clicking ok or
cancel on a dialog
On Tue, Dec 1, 2009 at 11:06 AM, James Turner zakal...@mac.com wrote:
On 1 Dec 2009, at 16:59, Curtis Olson wrote:
I've been observer quite frequent segfaults in the most recent version of
FlightGear. I've started running under gdb and so far the trend seems to be
that the crash is inside
On Tue, Dec 1, 2009 at 11:21 AM, Curtis Olson wrote:
On Tue, Dec 1, 2009 at 11:06 AM, James Turner wrote:
On 1 Dec 2009, at 16:59, Curtis Olson wrote:
I've been observer quite frequent segfaults in the most recent version
of FlightGear. I've started running under gdb and so far the trend
Here's an updated back trace with debugging symbols for plib ... the
segfault is on typeinfo for puDial() which is strange. Is this RTTI
related? I observe that the crash happens when the dialog box is being
closed, so could we have something out of order or a race condition between
the thread
Just to be clear, are you running with CullThreadPerCameraDrawThreadPerContext,
or what? How many of each?
On 12/01/2009 07:37 PM, Curtis Olson wrote:
Here's an updated back trace with debugging symbols for plib ... the
segfault is on typeinfo for puDial() which is strange. Is this RTTI
On Tue, Dec 1, 2009 at 1:32 PM, Tim Moore timo...@redhat.com wrote:
Just to be clear, are you running with
CullThreadPerCameraDrawThreadPerContext,
or what? How many of each?
That's a good question. I had been running with:
--prop:/sim/rendering/multithreading-mode=AutomaticSelection
This
On 12/01/2009 08:46 PM, Curtis Olson wrote:
On Tue, Dec 1, 2009 at 1:32 PM, Tim Moore timo...@redhat.com
mailto:timo...@redhat.com wrote:
Just to be clear, are you running with
CullThreadPerCameraDrawThreadPerContext,
or what? How many of each?
That's a good question. I
On Tue, Dec 1, 2009 at 3:36 PM, Tim Moore wrote:
No, I meant that 2.9.6+ is in svn.
Oh ok. I've been trying to live with downloadable releases, otherwise if
people are pulling different snapshots out of the repository at different
times we end up with something ... oh ... maybe like the
On 12/01/2009 08:32 PM, Tim Moore wrote:
Just to be clear, are you running with
CullThreadPerCameraDrawThreadPerContext,
or what? How many of each?
On 12/01/2009 07:37 PM, Curtis Olson wrote:
Here's an updated back trace with debugging symbols for plib ... the
segfault is on typeinfo for
11 matches
Mail list logo
