Some minor bugs

[Ceriy]

Ok. I wish to list some annoying problems when playing with PS.

These are minor bug, because I can play with these bugs.

First, the trainer part:
- When training some skills, I can buy only few points... then, the skill will become deselected: so if you want spend many points in that skill, you have to select the skill each point you buy. Maybe this is not a bug, but it's very strange. This happens with intelligence in the arena, and somewhere in Oja (sorry, i cannot remember). This happens always, but only on certain NPC. 
- When training Agility with Percival, sometimes the clients shutdown (it quits). This happens only when I've trained another skill with another NPC. If, in the game session, i train agility at first, the bug doesn't happen. 

Second, I want notice that running *after* starting repairing armor, my physical stamina don't lower until the weapon is repaired... So, if I repair a weapon for 280 secs, I can run to Oja without spending 1% of physical stamina. If I start repairing a weapon while running, and my physical stamina goes to 0%, I stops, but when I recover some stamina and I start to run, while running my stamina increase until 100% and stay stable until the weapon is repaired. 

Third: why I can mine with mental stamina at 0%? 

After this... I can start for hunting other bugs...

[AryHann]

Hi,

I can answer for what concerns the Agility thing.
If you get that the clients shutdown (I assume it actually crashes) and you get a pop up window that asks you if you want to save a Diagnostic file, then please, follow this http://hydlaa.com/smf/index.php?topic=26465.0!

About the other problems, I also recommend you to look at bugs.hydlaa.com and search if something you state is new or old and known.

[Xylaal]

Hi Ceriy- for the first one - next time it happens hit the 'eye' toggle just above and try it again...it seems some NPC's wont train you with more than one point unless that filter is switched.
Works for me 

[Ceriy]

Hi,

I can answer for what concerns the Agility thing.
If you get that the clients shutdown (I assume it actually crashes) and you get a pop up window that asks you if you want to save a Diagnostic file, then please, follow this http://hydlaa.com/smf/index.php?topic=26465.0!

I don't get any popup window... probably because I run the Linux binary. I searched for any *.dmp file (stay for dump, right?), but there is not any in the Planeshift directory. Where I can find it? However, good information.

[Ceriy]

Hi Ceriy- for the first one - next time it happens hit the 'eye' toggle just above and try it again...it seems some NPC's wont train you with more than one point unless that filter is switched.

Yeah, I didn't tought to this trick!

[AryHann]

Yeah, I assume that with Linux is different. The *.dmp files are just for Windows. I think you should be able anyway to get some sort of backtrace, but some Linux guru should pop up and say how ;-)

[Ceriy]

Yeah, I assume that with Linux is different. The *.dmp files are just for Windows. I think you should be able anyway to get some sort of backtrace, but some Linux guru should pop up and say how ;-)

I know there must be support in the binary to produce the core file... I know I can produce the core file running PS into gdb enviroment, but I dont like this fact... It should be nice to produce the core file naturally, without any programmer skill and enviroment...

Maybe, when I'll have some spare time, I could help this wonderfull project to improve itself... but actually I'm too busy to read and study the source code... 

Surely I want to improve Linux issues (for example arts audio support!  ). Maybe the next year 

[acraig]

Whenever I am debugging something in linux I normally turn core dumps on ( ulimit -c <max size> ) in my terminal and then run my client until it quits.  At that point I have a core.xxxx saved.  I normally do it a couple of times to get several core files.  Then I can use gdb to examine each one and if they are the same I know that I am looking for the same bug.   At that point I can begin to study the core files more deeply and try to fix the bug.  Of course, my build is the fully debug build which gives me all sorts of nice information for tracking down the bugs. 

The same sort of thing happens on the server as well.   Whenenver the server crashes it creates  a core file and then emails out to many team members a stack trace.  If we need to we can log on to the server machine and examine the core files more closely to figure out what is needed to figure out the bug.   In some cases it's really easy to figure out, other times it can take several people several days to understand what the problem is.

[Xordan]

The linux binary will produce no useful output for debugging, mainly because the release mode optimizations screw up any useful info, and I strip them of any debugging symbols to reduce size.

[AryHann]

Then, a good way is to try to build the client yourself and eventually try to get again the problem... so you will be able to track it down, since you shouldn't have the optimization made by Xordan...

I hope I am correct :-)

[Ceriy]

So, I can compile (with debuggin option) the PS client directly from the current CVS? If so, I'm glad to help  . Where core files are sent?

[Lanarel]

Second, I want notice that running *after* starting repairing armor, my physical stamina don't lower until the weapon is repaired... So, if I repair a weapon for 280 secs, I can run to Oja without spending 1% of physical stamina. If I start repairing a weapon while running, and my physical stamina goes to 0%, I stops, but when I recover some stamina and I start to run, while running my stamina increase until 100% and stay stable until the weapon is repaired. 

These are at least two problems, covered in several bug reports. For not loosing stamina while repairing the fix seems simple (I added a fix in one of the bugreports), however looking at the code it seems that TomT left it out on purpose (something about stamina not being discussed).
The being able to run while repairing is more complicated. Adding a test to stop repairing when moving fast (as is done for spell casting) is easy, but it would also stop turning ore in molten metal (transformations). It seems that stopping repairing was removed from the code (commented out) by TomT when he implemented the more complex crafting.