Hi!
When starting fg with an invalid aircraft, it segfaults after printing the
message:
Cannot find specified aircraft: 777
Program received signal SIGSEGV, Segmentation fault.
0x77970d44 in pthread_mutex_lock () from /lib64/libpthread.so.0
(gdb) thread apply all bt
Thread 5 (Thread 0
On 08/03/2012 09:45 AM, James Turner wrote:
>
>
>
>
> On 2 Aug 2012, at 20:32, Erik Hofman wrote:
>
>> Hi,
>>
>> Seems like Canvas causes a reproducible segfault with the latest git
>> version (master). I'm using 32 bit Ubuntu 12.04
>
> Yep, this is my fault for causing a naming clash. Just commen
On 2 Aug 2012, at 20:32, Erik Hofman wrote:
> Hi,
>
> Seems like Canvas causes a reproducible segfault with the latest git
> version (master). I'm using 32 bit Ubuntu 12.04
Yep, this is my fault for causing a naming clash. Just comment out
initNasalCanvas in NasalSys.cxx for now, I'll pus
Hi,
Seems like Canvas causes a reproducible segfault with the latest git
version (master). I'm using 32 bit Ubuntu 12.04:
Program received signal SIGSEGV, Segmentation fault.
0x0884a935 in resize ()
(gdb) bt
#0 0x0884a935 in resize ()
#1 0x0884b21d in naiHash_newsym ()
#2 0x08843149 in setupA
On 16 Sep 2011, at 10:37, Andreas Gaeb wrote:
> I just tried to run with real weather fetch, but the network cable was
> not plugged. This produced a segfault after about a minute, see below.
> Somewhere the information that the lookup has finally failed seems to
> get lost. After re-plugging
Hello,
I just tried to run with real weather fetch, but the network cable was
not plugged. This produced a segfault after about a minute, see below.
Somewhere the information that the lookup has finally failed seems to
get lost. After re-plugging the cable, everything was fine.
Best regards,
Am 27.07.2011 11:58, schrieb Durk Talsma:
>
> On 27 Jul 2011, at 11:54, Torsten Dreyer wrote:
>>
>> Here is another one to chew on: How to I close the ATC Dialog?
>> It pops up again every time I hit the Cancel button or press Escape.
>>
>
> Great that it works now!
>
> With regard to the dialog, j
On 27 Jul 2011, at 11:54, Torsten Dreyer wrote:
>
> Here is another one to chew on: How to I close the ATC Dialog?
> It pops up again every time I hit the Cancel button or press Escape.
>
Great that it works now!
With regard to the dialog, just press the apostrophe (') key again. (Note that
t
Am 27.07.2011 11:04, schrieb Durk Talsma:
>>
>> This one happen also at KNID with 87bd2bf, AFAIK, KNID doesn't have any
>> ground network. In the meantime I reverted to friday evening FG
>> (3723de5) and then it was OK again.
>>
>
> I'm currently committing a fix for this problem. As I already susp
>
> This one happen also at KNID with 87bd2bf, AFAIK, KNID doesn't have any
> ground network. In the meantime I reverted to friday evening FG
> (3723de5) and then it was OK again.
>
I'm currently committing a fix for this problem. As I already suspected, the
problem was introduced when fixing
Le 26/07/2011 22:45, Durk Talsma a écrit :
> Hi Torsten,
> On 26 Jul 2011, at 22:34, Torsten Dreyer wrote:
>
>> Am 26.07.2011 22:26, schrieb Durk Talsma:
>>> Hi Torsten,
>>>
>>> Thanks for the report. I can confirm the crash, which means that I'm
>>> optimistic that I find a solution tomorrow. I'v
On Jul 26, Torsten Dreyer wrote:
> Just noticed: happens at EHAM, too. c172p, no parkpos, no live weather
> (Fair Weather), a few seconds after takeoff from rwy 18R.
"ATC Services in range" button from the radio panel (F12) also does no
longer show any airport frequencies (testing from EHAM with
Hi Torsten,
On 26 Jul 2011, at 22:34, Torsten Dreyer wrote:
> Am 26.07.2011 22:26, schrieb Durk Talsma:
>> Hi Torsten,
>>
>> Thanks for the report. I can confirm the crash, which means that I'm
>> optimistic that I find a solution tomorrow. I've just seen a similar report
>> at the forum, so I
Am 26.07.2011 22:26, schrieb Durk Talsma:
> Hi Torsten,
>
> Thanks for the report. I can confirm the crash, which means that I'm
> optimistic that I find a solution tomorrow. I've just seen a similar report
> at the forum, so I should have at least two test cases for this.
Just noticed: happens a
Hi Torsten,
Thanks for the report. I can confirm the crash, which means that I'm optimistic
that I find a solution tomorrow. I've just seen a similar report at the forum,
so I should have at least two test cases for this.
cheers,
Durk
---
Am 26.07.2011 22:00, schrieb Torsten Dreyer:
> Am 26.07.2011 18:35, schrieb Durk Talsma:
>>
>> On 26 Jul 2011, at 07:43, Torsten Dreyer wrote:
>>
>>> Am 25.07.2011 23:19, schrieb Durk Talsma:
Okay, I'll have a look. Just to make sure: This is a problem that only
shows up during program s
Am 26.07.2011 18:35, schrieb Durk Talsma:
>
> On 26 Jul 2011, at 07:43, Torsten Dreyer wrote:
>
>> Am 25.07.2011 23:19, schrieb Durk Talsma:
>>> Okay, I'll have a look. Just to make sure: This is a problem that only
>>> shows up during program shutdown?
>>
>> Correct - sorry, I didn't mention that
On 26 Jul 2011, at 07:43, Torsten Dreyer wrote:
> Am 25.07.2011 23:19, schrieb Durk Talsma:
>> Okay, I'll have a look. Just to make sure: This is a problem that only shows
>> up during program shutdown?
>
> Correct - sorry, I didn't mention that.
>
It should be fixed now. As it turned out the
Am 25.07.2011 23:19, schrieb Durk Talsma:
>
> On 25 Jul 2011, at 22:54, Torsten Dreyer wrote:
>
>>>
>>> Sounds like a good idea. In any case, I have just commited a fix that
>>> should solve the runway initialization problem.
>> OK - that fixed the initialization issue.
>> looking at the code, the
On 25 Jul 2011, at 22:54, Torsten Dreyer wrote:
>>
>> Sounds like a good idea. In any case, I have just commited a fix that should
>> solve the runway initialization problem.
> OK - that fixed the initialization issue.
> looking at the code, there is still one rwy initialization on line 517
>
>
> Sounds like a good idea. In any case, I have just commited a fix that should
> solve the runway initialization problem.
OK - that fixed the initialization issue.
looking at the code, there is still one rwy initialization on line 517
in createClimb() like those you just moved.
And I now get a
On 25 Jul 2011, at 21:32, Torsten Dreyer wrote:
> It's probably a good idea to initialize properties in the constructor to
> NULL and check their values before usage in the createXXX methods
> (assert() is your friend).
> Might cause some long debugging nights later, once you forgot how your
>
> Okay, I'll have a look. I *thought* that I had fixed all initialization
> issues this morning, but maybe I introduced a related problem. I expect to
> find a solution later this evening. Thanks for reporting!
It's probably a good idea to initialize properties in the constructor to
NULL and ch
On 25 Jul 2011, at 20:59, Torsten Dreyer wrote:
>
>> Looks like I missed pushing part of my local changes onto gitorious. It
>> should be working now (apart from updating hte MSVC build files).
> Hi Durk,
>
> starting at KSFO without a parkpos define, I get a segfault in
> AIFlightPlanCreate
> Looks like I missed pushing part of my local changes onto gitorious. It
> should be working now (apart from updating hte MSVC build files).
Hi Durk,
starting at KSFO without a parkpos define, I get a segfault in
AIFlightPlanCreate::createTakeOff()
because firstFlight is set to false and the
On Tuesday 31 May 2011 14:17:23 Mathias Fröhlich wrote:
> So, what to do:
>
> The real solution is hard. Tim effecs code *probably* shows how to solve
> this. I have never double checked if this is done in a waterproof way, but
> I would guess this is ...
>
> A solution that might at least work
Good morning,
On Monday, May 30, 2011 19:54:31 ThorstenB wrote:
> On 30.05.2011 19:25, Stefan Seifert wrote:
> > The segfault happens when the main loop thread tries to
> > access GL information. I know next to nothing about openGL programming
> > but I seem to recall that it's not allowed to acc
On 30.05.2011 19:25, Stefan Seifert wrote:
> The segfault happens when the main loop thread tries to
> access GL information. I know next to nothing about openGL programming but I
> seem to recall that it's not allowed to access the same GL context in
> different
> threads. So how is this supposed
On Friday 13 May 2011 11:03:24 Anders Gidenstam wrote:
> Presumably it will also increase the risk of triggering any race condition
> and/or unsynchronized data access bugs that may be lurking in the code.
> There are some known ones (e.g. during the creation of a particle
> system) but there coul
On Fri, 13 May 2011, Stefan Seifert wrote:
> multithreading-mode is disabled by default with a note, that it breaks
> screenshots. Is this the only reason or is it known not to be stable?
Presumably it will also increase the risk of triggering any race condition
and/or unsynchronized data access
Hi!
While trying to get some double digit frame rates out of FG next, I tried to
enable OSG multi threading in preferences.xml, but that leads to a segfault:
#0 0x772af357 in glGetString () from /usr/lib64/libGL.so.1
#1 0x00ab9b3a in SGIsOpenGLExtensionSupported (extName=0xbe07
On Fri, Feb 4, 2011 at 3:10 PM, Ivan Ngeow wrote:
> On 4 February 2011 22:44, Martin Spott wrote:
>
>> and maybe restore individual files from here - or configure
>> with "--disable-atcdcl", which, as far as I remember, has recently been
>> re-enabled by default.
>>
>
> Yes I vaguely rem
On 4 February 2011 22:44, Martin Spott wrote:
> and maybe restore individual files from here - or configure
> with "--disable-atcdcl", which, as far as I remember, has recently been
> re-enabled by default.
>
Yes I vaguely remember that too. Unfortunately,
configure:18083: WARNING: Unre
Ivan Ngeow wrote:
> And the segfault remains, same location, after restoring this file. Perhaps
> there are other files removed?
Well, quite a few files had been removed, but none of the other
removals is crashing FlightGear. If you think 'your' crash is related
to one of the other file removals
On 4 February 2011 21:49, Martin Spott wrote:
> Martin Spott wrote:
> >
> >> The file "$FG_ROOT/ATC/default.transmissions" is missing from the Base
> >> Package - and 'touch'ing an empty file just leads to FG eating all
> >> memory.
> >
> > Get it from here:
> >
> >
> http://mapserver.flightgear.
Martin Spott wrote:
> Martin Spott wrote:
>
>> The file "$FG_ROOT/ATC/default.transmissions" is missing from the Base
>> Package - and 'touch'ing an empty file just leads to FG eating all
>> memory.
>
> Get it from here:
>
>
> http://mapserver.flightgear.org/git/gitweb.pl?p=fgdata;a=blob_plain
Ivan Ngeow wrote:
> On 4 February 2011 19:07, Martin Spott wrote:
>> Get it from here:
>>
>>
>> http://mapserver.flightgear.org/git/gitweb.pl?p=fgdata;a=blob_plain;f=ATC/default.transmissions;hb=f8c697ef4274fef4fd821d3b9316bbda1030a05f
>>
>
>
> nup, this link doesn't work.
Maybe your MUA broke
On 4 February 2011 19:07, Martin Spott wrote:
> Martin Spott wrote:
>
> > The file "$FG_ROOT/ATC/default.transmissions" is missing from the Base
> > Package - and 'touch'ing an empty file just leads to FG eating all
> > memory.
>
> Get it from here:
>
>
> http://mapserver.flightgear.org/git/gitwe
Martin Spott wrote:
> The file "$FG_ROOT/ATC/default.transmissions" is missing from the Base
> Package - and 'touch'ing an empty file just leads to FG eating all
> memory.
Get it from here:
http://mapserver.flightgear.org/git/gitweb.pl?p=fgdata;a=blob_plain;f=ATC/default.transmissions;hb=f8c6
Ivan Ngeow wrote:
> Today's SG, FG and fgdata.
>
> FreeBSD-8.0.
Same here (on Debian Linux).
The file "$FG_ROOT/ATC/default.transmissions" is missing from the Base
Package - and 'touch'ing an empty file just leads to FG eating all
memory.
Cheers,
Martin.
--
Unix _IS_ user friendly - i
Today's SG, FG and fgdata.
FreeBSD-8.0.
0x080e91e9 in FGATCMgr::update (this=0x537fbf60, dt=0.0083332)
at ATCmgr.cxx:119
119 (*atc_list_itr).second->Update(dt * atc_list->size());
(gdb) bt
#0 0x080e91e9 in FGATCMgr::update (this=0x537fbf60,
dt=0.0083332)
On Sun, Dec 5, 2010 at 9:18 AM, Jeff Taylor wrote:
> On 02/12/10 12:05 AM, Tim Moore wrote:
> > Can you move up the stack into SGText::UpdateCallback::operator() and
> > see what is being passed to createUTF8EncodedString?
> >
> > Thanks,
> > Tim
> OK, this is bugging me. I needed to recompile O
On Sun, 05 Dec 2010 00:18:12 -0800, Jeff wrote in message
<4cfb4ac4.4030...@gmail.com>:
> On 02/12/10 12:05 AM, Tim Moore wrote:
> > Can you move up the stack into SGText::UpdateCallback::operator()
> > and see what is being passed to createUTF8EncodedString?
> >
> > Thanks,
> > Tim
> OK, this is
See also http://fedoraproject.org/wiki/Xorg/Debugging
Stefan
2010/12/5 Olaf Flebbe :
> Hi,
>
>> I'll post a bug on Fedora's bug
>> tracker, but if anyone using this list knows what kind of information I
>> can provide to them, that would help.
>
> Please have a look at http://dri.freedesktop.or
Hi,
> I'll post a bug on Fedora's bug
> tracker, but if anyone using this list knows what kind of information I
> can provide to them, that would help.
Please have a look at http://dri.freedesktop.org/wiki
Specifically TestingAndDebugging/Capturing debugging info without networking
Additional
> Now it starts, but strangely my
> system hard locks (frozen mouse, frozen screen) a few minutes after
> starting, which means that this is almost certainly a bug in the Intel
> display drivers.
Don't know if this helps you, but I had a lockup error when I ran four NVidia
GTX460 in one system.
On 02/12/10 12:05 AM, Tim Moore wrote:
> Can you move up the stack into SGText::UpdateCallback::operator() and
> see what is being passed to createUTF8EncodedString?
>
> Thanks,
> Tim
OK, this is bugging me. I needed to recompile OSG with debugging
symbols, so I did a pull from SVN first, which
Can you move up the stack into SGText::UpdateCallback::operator() and see
what is being passed to createUTF8EncodedString?
Thanks,
Tim
On Thu, Dec 2, 2010 at 8:46 AM, Jeff Taylor wrote:
> On 29/11/10 12:45 AM, Erik Hofman wrote:
> > So it looks like to be a JSBSim problem, now you could try to
On 29/11/10 12:45 AM, Erik Hofman wrote:
> So it looks like to be a JSBSim problem, now you could try to test a
> turbine powered aircraft like the F-16 to try to pinpoint the problem.
> It would probably be a good idea to try running FlightGear inside a
> debugger an provide a backtrace if possibl
On Mon, 2010-11-29 at 09:45 +0100, Erik Hofman wrote:
> So it looks like to be a JSBSim problem, now you could try to test a
> turbine powered aircraft like the F-16 to try to pinpoint the problem.
> It would probably be a good idea to try running FlightGear inside a
> debugger an provide a backtra
On Sun, 2010-11-28 at 23:50 -0800, Jeff Taylor wrote:
> OK. So the Cub works, the ufo works. (also updated to current git)
> Maybe you meant --disable-sound? I tried both --enable-sound, and
> --disable sound, and neither worked. Maybe it's something more specific
Ah yes off course..
> to
On 28/11/10 02:05 AM, Erik Hofman wrote:
> On Sat, 2010-11-27 at 10:28 -0800, Jeff Taylor wrote:
>> Everything is in sync. I just updated it now, and it still gets the
>> same thing.
>>
>> I ran it with all the defaults, like fgfs
>> --fg-root=/home/jeff/Computer/fg/flightgear/fgdata/
>>
>> Lookin
On Sat, 2010-11-27 at 10:28 -0800, Jeff Taylor wrote:
> Everything is in sync. I just updated it now, and it still gets the
> same thing.
>
> I ran it with all the defaults, like fgfs
> --fg-root=/home/jeff/Computer/fg/flightgear/fgdata/
>
> Looking again, it must be the C172P. Running with -
On 27/11/10 12:59 AM, Erik Hofman wrote:
> On Fri, 2010-11-26 at 17:36 -0800, Jeff Taylor wrote:
>> Hi all,
>>
>> I'm getting a segfault in the current git version. It happens on
>> startup, every time.
>>
>> I'd like to get Flightgear running. I intend to do a little bit of
>> coding, but I need
On Fri, 2010-11-26 at 17:36 -0800, Jeff Taylor wrote:
> Hi all,
>
> I'm getting a segfault in the current git version. It happens on
> startup, every time.
>
> I'd like to get Flightgear running. I intend to do a little bit of
> coding, but I need to get it running normally before I can make
Hi all,
I'm getting a segfault in the current git version. It happens on
startup, every time.
I'd like to get Flightgear running. I intend to do a little bit of
coding, but I need to get it running normally before I can make
changes. I know how to get more information, but I'm not sure what
yes now I know ;) thanks to Jester on #flightgear, using gdb and
valgrind he found out what was wrong: hopefully he knows how to correct
the problem too.
So the "problem" comes from the openAL side, and a correct config in
~/.alsoftrc brings back a nice FG windows ready to make tests on the
zk
2010/11/14 Sébastien MARQUE :
>
> so I've created some logs, hoping they could help:
That's all very nice, but you left out the single most important one:
a gdb backtrace :)
--
Csaba/Jester
--
Centralized Desktop Delive
Hi all,
I'm used to compile OSG/svn, SG/git and FG/git on a debian sid system
using gcc version 4.4.5 (Debian 4.4.5-7).
I'm facing a segfault problem for two days now (but I couldn't test
before for more than one week). I've tried different solutions as put
away ~/.fgfs/autosave.xml, then ~/.f
Hi,
Using git, I have a segfault :(
Here the backtrace :
(gdb) backtrace full
#0 0x7fffcf755110 in ?? ()
No symbol table info available.
#1 0x00808144 in fgUpdate3DPanels () at panelnode.cxx:34
i = 3
#2 0x00438c6e in SGHUDAndPanelDrawable::drawImplementation
(this
Tim Moore wrote:
> As the subject line says, I'm seeing a segfault in pulseaudio library
> code on Fedora 12. I just upgraded, so I can't really say when this was
> introduced, but "old" code which doesn't use Erik's sound manager
> development of recent months doesn't show this behaviour.
Ther
As the subject line says, I'm seeing a segfault in pulseaudio library code
on Fedora 12. I just upgraded, so I can't really say when this was
introduced, but "old" code which doesn't use Erik's sound manager
development of recent months doesn't show this behaviour.
The available sound devices are:
Hi,
Program received signal SIGSEGV, Segmentation fault.
0x085fff40 in SGGeodesy::SGGeodToCart (geod=..., cart=...) at
SGGeodesy.cxx:119
119 SGGeodesy::SGGeodToCart(const SGGeod& geod, SGVec3& cart)
Current language: auto
The current source language is "auto; currently c++".
(gdb) backtrace f
To complete backtrace :
(gdb) backtrace full
#0 0x085b15e0 in SGGeodesy::SGGeodToCart (ge...@0x19, ca...@0xbff93d40)
at SGGeodesy.cxx:100
h = 78.0288004
n = -2.9997860811925778
#1 0x084698da in FGPositioned::cart (this=0x11)
at /usr/local/include/simgear/math/SGVec3.hxx:1
Hi,
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6215730 (LWP 28660)]
0x085b15e0 in SGGeodesy::SGGeodToCart (ge...@0x19, ca...@0xbff93d40) at
SGGeodesy.cxx:100
100 SGGeodesy::SGGeodToCart(const SGGeod& geod, SGVec3& cart)
(gdb) list
95geod.setLatitudeRad
On vendredi 09 janvier 2009, James Turner wrote:
> On 9 Jan 2009, at 13:18, gerard robin wrote:
> > get same kind of crash here with gdb:
> >
> > [Thread debugging using libthread_db enabled]
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0088c7c9 in
> > FGAirport::getIt
On 9 Jan 2009, at 13:18, gerard robin wrote:
> get same kind of crash here with gdb:
>
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0088c7c9 in
> FGAirport::getIteratorForRunwayIdent(std::string const&)
> const ()
> Current
> On 9 Jan 2009, at 11:17, James Turner wrote:
> > If anyone else is seeing this (or isn't, with a clean, up-to-date
> > tree), that'd be very helpful information, since I'm not.
>
> Never mind, I can reproduce this locally on my (Vmware) ubuntu, so
> it's something Linux-y, not a build issue.
>
>
On vendredi 09 janvier 2009, James Turner wrote:
> On 9 Jan 2009, at 11:17, James Turner wrote:
> > If anyone else is seeing this (or isn't, with a clean, up-to-date
> > tree), that'd be very helpful information, since I'm not.
>
> Never mind, I can reproduce this locally on my (Vmware) ubuntu, so
> It's not clear to me if this as a clean build (in the code sense) -
> you say fresh autogen.sh and configure, but that doesn't necessarily
> imply existing object files get rebuilt (or does it?)
Oh sorry - forgot to mention that I also executed "make clean"
>
> If anyone else is seeing this (or
On 9 Jan 2009, at 11:17, James Turner wrote:
> If anyone else is seeing this (or isn't, with a clean, up-to-date
> tree), that'd be very helpful information, since I'm not.
Never mind, I can reproduce this locally on my (Vmware) ubuntu, so
it's something Linux-y, not a build issue.
Will commi
> If anyone else is seeing this (or isn't, with a clean, up-to-date
> tree), that'd be very helpful information, since I'm not.
I did some digging with the following result:
The code crashes when calling apt->getRunwayByIdent for airport OAKB and
runway 29 for the OAKB 29 CAT II ILS.
With some d
One more trace,
with log-level=debug, the last thing I see is:
Splash screen progress reading aircraft list
Splash screen progress reading airport & navigation data
Loading Airport Database ...
Data file version = 810
End of file reached
[FINISHED LOADING]
Loading Navaid Databases
localizer:IITL,
On 9 Jan 2009, at 10:42, Torsten Dreyer wrote:
> with cvs as of today, I receive a segfault shortly after starting
> fgfs;
> No command line args, no .fgfsrc, no .fgfs directory, standard
> preferences.xml
> fresh autogen.sh and configure
Almost certainly my fault - do you known when you las
Hi,
with cvs as of today, I receive a segfault shortly after starting fgfs;
No command line args, no .fgfsrc, no .fgfs directory, standard preferences.xml
fresh autogen.sh and configure
Here is a backtrace
Program received signal SIGSEGV, Segmentation fault.
FGAirport::getIteratorForRunwayIdent
79::As of 1.9.0, changing "helvetica-bold" to "helvetica" in e.g.
Instruments/altimeter.xml causes the cockpit/panel loader to
segfault.
a) It would be nice if helvetica were supported.
b) Failing that, if helvetica is called for it would be nice to print
a warning and substitute some s
74:: As of 1.9.0, the cockpit/panel system will segfault if the
switch statement is omitted from a layer that has
nothing but sublayers. Actually you don’t even need any sublayers; an
empty layer also segfaults:
SIGSEGV
The same of course applies to layers of the undocume
On Sun, Sep 28, 2008 at 6:50 PM, Oliver Schroeder <[EMAIL PROTECTED]> wrote:
> Hi List.
>
> I'm experiencing segfaults with the current cvs head version of flightgear
> (osg) when using the cessna CitationX aircraft.
> The segfault happens more or less shortly after starting the engines. This
> seg
Hi List.
I'm experiencing segfaults with the current cvs head version of flightgear
(osg) when using the cessna CitationX aircraft.
The segfault happens more or less shortly after starting the engines. This
segfaults happens too with a few additional aircrafts (which I can not name
now, I have
On jeu 28 août 2008, Durk Talsma wrote:
> Hi Tim,
>
> On Wednesday 27 August 2008 15:37:19 Tim Moore wrote:
> > This is great! We can't call osgDB:SharedStateManager::share from the
> > database pager thread. I'll check in a fix soon.
>
> Great to hear that this stack trace was useful. :-)
>
> Chee
Hi Tim,
On Wednesday 27 August 2008 15:37:19 Tim Moore wrote:
>
> This is great! We can't call osgDB:SharedStateManager::share from the
> database pager thread. I'll check in a fix soon.
>
Great to hear that this stack trace was useful. :-)
Cheers,
Durk
-
Durk Talsma wrote:
>
> FWIW, I;m seeing an occasional segfault. Today, I managed to trap it using
> gdb. below is the complete stack trace. IIRC, 2D texture loading has been
> giving occasional problems. This particular error occurred in my new traffic
> manager version of Flightgear. It doesn
On Sunday 24 August 2008 04:38:36 Csaba Halász wrote:
> At least 3 of us get immediate segfault most of the time if starting
> at LFPG. I got various backtraces, mostly from OSG.
> Sometimes there is a warning similar to this:
> Warning: deleting still referenced object 0xb2de7f08 of type
> 'PN3osg
On Sun, Aug 24, 2008 at 04:38:36AM +0200, Csaba Halász wrote:
> At least 3 of us get immediate segfault most of the time if starting
> at LFPG. I got various backtraces, mostly from OSG.
Me too , i have many segfaults . My context :
- Phenom 9750 Quad-Core / GeForce 8800 GT
- linux 2.6.25 ( x
On Sun, 2008-08-24 at 04:38 +0200, Csaba Halász wrote:
> At least 3 of us get immediate segfault most of the time if starting
> at LFPG. I got various backtraces, mostly from OSG.
> Sometimes there is a warning similar to this:
> Warning: deleting still referenced object 0xb2de7f08 of type
> 'PN3os
At least 3 of us get immediate segfault most of the time if starting
at LFPG. I got various backtraces, mostly from OSG.
Sometimes there is a warning similar to this:
Warning: deleting still referenced object 0xb2de7f08 of type
'PN3osg10ReferencedE'
the final reference count was 0, memory corruptio
Csaba Halász wrote:
> On Sun, May 18, 2008 at 1:01 AM, alexis bory <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> FG segfaults here short after or during launch when started with MP
>> enabled and when in a crowded aera, it may depend of the MP models
>> loaded but if yes, I didn't find wich one.
>>
On Sun, May 18, 2008 at 1:01 AM, alexis bory <[EMAIL PROTECTED]> wrote:
> Hi,
>
> FG segfaults here short after or during launch when started with MP
> enabled and when in a crowded aera, it may depend of the MP models
> loaded but if yes, I didn't find wich one.
I guess you are missing an osg ima
alexis bory wrote:
> Hi,
>
> FG segfaults here short after or during launch when started with MP
> enabled and when in a crowded aera, it may depend of the MP models
> loaded but if yes, I didn't find wich one.
Note: the problem was the same with FG-OSG compiled on 2008-05-05.
> Config: FG
Hi,
FG segfaults here short after or during launch when started with MP
enabled and when in a crowded aera, it may depend of the MP models
loaded but if yes, I didn't find wich one.
Config: FG OSG updated and compiled this evening, Linux flonk
2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2
Tobias Ramforth wrote:
> Hi!
>
>> Everytime. I'll try rolling back to an older OSG when I get a chance.
>
> Are you sure you recompiled every single lib using up-to-date sources
> (CVS/SVN)?
> I encountered a segfault, as well, but I forgot to recompile simgear.
> Double check the compilation o
Hi,
I've already faced this kind of comportment, until I checked for any
reason /usr/bin/gcc and found it was linked to gcc-4.2, but I am used to
compile all the FG stuff with gcc-4.3 from a long time. Indeed I surely
have changed the link one day to do something, and stupidly forgot to
link i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Seifert wrote:
| On Sunday, 13. April 2008, James Sleeman wrote:
|> On Sat, 2008-04-12 at 14:59 +0100, LeeE wrote:
|>> Does it segfault every time or is it inconsistent? I'm about a week
|> Everytime. I'll try rolling back to an older OSG when
On Sunday, 13. April 2008, James Sleeman wrote:
> On Sat, 2008-04-12 at 14:59 +0100, LeeE wrote:
> > Does it segfault every time or is it inconsistent? I'm about a week
>
> Everytime. I'll try rolling back to an older OSG when I get a chance.
Just a note: I'm having the same problem since 2.3.7.
Hi!
Everytime. I'll try rolling back to an older OSG when I get a chance.
Are you sure you recompiled every single lib using up-to-date sources
(CVS/SVN)?
I encountered a segfault, as well, but I forgot to recompile simgear.
Double check the compilation order, too!
Regards,
Tobias
begi
On Sat, 2008-04-12 at 14:59 +0100, LeeE wrote:
> Does it segfault every time or is it inconsistent? I'm about a week
Everytime. I'll try rolling back to an older OSG when I get a chance.
--
James Sleeman <[EMAIL PROTECTED]>
-
On Saturday 12 April 2008 06:03, James Sleeman wrote:
> Am I the only one getting segfaults on a full compile of the
> latest HEAD or is it just not working at the moment. Full update
> and compile of everything, SimGear, OSG, Plib1.8.5, flightgear
> with --enable-osgviewer, and data all up to dat
James Sleeman wrote:
> Am I the only one getting segfaults on a full compile of the latest HEAD
> or is it just not working at the moment. Full update and compile of
> everything, SimGear, OSG, Plib1.8.5, flightgear with --enable-osgviewer,
> and data all up to date. Segfaults as soon as it tries
On Sat, 2008-04-12 at 10:35 +0200, Anders Gidenstam wrote:
> Double check that OSG finds it's plugins and that the plugin for that
> image type exist (presumably FlightGear uses the formats .rgb, PNG and
> JPEG?).
{prefix}/lib/psgPlugins-2.3.6 contains plugins for rgb, png and jpeg.
But how ca
On Sat, 12 Apr 2008, James Sleeman wrote:
> Am I the only one getting segfaults on a full compile of the latest HEAD
> or is it just not working at the moment. Full update and compile of
> everything, SimGear, OSG, Plib1.8.5, flightgear with --enable-osgviewer,
> and data all up to date. Segfaul
1 - 100 of 128 matches
Mail list logo
