Ampere K. Hardraade wrote:
Would that change anything? If they did try the pre-releases and reported
problems, would the final release really be delayed until the problem is
fixed? Why do I get the feeling that they would be the ones to get blamed
like what is happening now?
Were those people who are having problems offered the chance to help fixed the
problem? Where are responses like "we will look into the problem, but we
need you to investigate the problems for us by doing this and this, since we
don't have the hardware"? How about messages like "let's have a discussion
over the IRC at certain time, and we can track down the issue"? Why am I
only seeing responses that automatically assume the problem is from the user
side? Why am I only seeing unproductive responses like "you didn't
contribute, so you don't deserved to get help", "fix it yourself", and
"upgrade your hardware"?
We should try to be fair to each other here. This is a *hard* problem,
not an easy one. The fact is that it is not fixed and that is very
frustrating to those that are seeing the problem. But how do we move
forward here? You are asking developers to fix a bug they can't
reproduce. That is almost always really hard. It means someone else
has to be the eyes and ears remotely, and that person probably doesn't
have the tools setup to be very helpful.
Let me ask for some information, with no idea if this will help us move
forward or not, but it's an attempt.
1. Have you isolated which hardware, platform, drivers are affected? I
hear that some people running ATI hardware have no problems. Can we
nail down exactly the scope of the problem? That may or may not be
helpful, but it can't hurt.
2. Can you try building FG with debugging symbols (-g) which I think is
the default. Run fgfs inside a debugger (such as gdb) and when you get
a crash, copy the backtrace (i.e. the output of the 'where' command.)
This is something that needs to be done on the machine with the
problem. So you or someone who at least can compile from source is
going to have to do it. That may or may not tell us something either,
but again it's a starting point.
Thanks,
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
