Latest Linux Mesh viewer crashes upon connection
Author |
Message |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 244
|
Hallo!
I have no idea what the problem is. The viewer starts, I log in, and the moment it finishes connecting it crashes. I ran it from a terminal box, so I can attach the output.
If you need me to attach anything else, please ask.
Thanks
|
2011-10-09 14:04:40 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6030
|
Please, provide the stack_trace.log file.
|
2011-10-09 18:55:10 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 244
|
Here you are.
|
2011-10-09 20:39:50 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6030
|
Well, for a start, there is a problem with your audio driver: the viewer can't find a way to initialize audio on your system... Then there's that weird folder name you installed the viewer into (with non-printable characters in the name !): I suggest you try reinstalling it in a folder with plain ASCII characters in its name...
Finally, the stack_trace.log file doesn't give any useful info, and since you didn't provide the corresponding SecondLife.log file, it's impossible to tell where the viewer crashed.
|
2011-10-09 22:35:20 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 244
|
Firstly, thank you for your reply.
I noticed the issue about the sound driver myself, I'll work on it, but surely it can't be reason the viewer crashes. The same holds for the directory I am running it from, since I do this every time I am testing something. In any case, Phoenix and Imprudence work like that, so that shouldn't be a problem.
As for SecondLife.log, I am attaching it now.
Thanks again, Gordon
|
2011-10-10 10:31:49 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6030
|
Yes, it could, in case I would have forgotten to test for a NULL gAudiop pointer somewhere in the code... Please, do not make assumptions about what is possible or not when you don't know the code itself... Again, that's just a gratuitous assumption. Please, proceed as I asked you to, and install the viewer in a directory which path only contains plain ASCII characters to see if it works. I guess I should have made myself clearer (even though the rules for this forum are pretty clear already). I need BOTH the SecondLife.log and the corresponding stack_trace.log, not one from a crash and the other from a later crash...
|
2011-10-10 13:51:49 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 244
|
Henri,
There really isn't any need for non-polite replies. The point is to find what's wrong, either with the viewer or —quite possibly— with my computer. And if I didn't like your viewer I would simply reject it as I did with LL3 and FS3. I do like it, and I appreciate your hard work and dedication, and this is why I signed up in your forum and try to find out what is wrong, so I can keep using it and promote it to all the friends who prefer the v1 gui.
Anyway, I moved the whole directory to ~/, deleted my ~/.secondlife and reran the application. I am attaching the new files. If you need anything else, please ask.
Gordon
|
2011-10-10 14:31:10 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6030
|

Oh, and where exactly would have I been impolite ?... Did I swear or call you names ?... I don't think so ! On the other hand, if you perceived some irritation in my tone, then you got it right: I'm a bit tired to repeat the same things over and over again when I wrote everything in rules, FAQs or former posts that obviously no one cares to read... Or to have to move around messages that are obviously posted in the wrong forum when it would only take three seconds for the poster to choose the right one in the first place by simply reading the subject of the forums... Mind you, my free time is *limited*, and I develop the Cool VL Viewer during this limited free time. The time I take to write for the Nth time the same thing in the forum (or to move topics around, or to merge topics with older ones which already gave the answers to the questions) can't be used for better and more productive purposes, including for improving the viewer code. Thanks. Alas, the logs are inconclusive as to why the viewer crashed. The stack trace log doesn't even give any pointer in the viewer code (beside pointers to the stack dumping code itself)... Well, if you want me to find and squish that bug, I need you to run the viewer under gdb and provide me with the backtrace. See this message for how to do it.
|
2011-10-10 17:35:31 |
|
 |
g0rd0ngrfr33mailgr
Joined: 2011-09-27 11:18:31 Posts: 244
|
Fine. I did, but we have nothing more detailed.
|
2011-10-10 18:01:40 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6030
|
Oh yes, we have !... It relates to a backport from v3 I did in v1.26.1.9... I'll create a test binary with that change reverted so that you can test it.
|
2011-10-10 20:35:18 |
|
|
Who is online |
Users browsing this forum: No registered users and 19 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|