linux x86_64 PS Bugs

[RalphMW]

Hi Folks,

Now that I have a running PSclient on my new machine (amd64) I want to report bugs to help increase development and stability on that platform.

But PS for linux doesn\'t have a dump-file like the windows version. So the question is: what infos do u need and how to gather it from my system?

client output, gdb backtrace, ...
And where to post, upload or mail these things to?

Machine:
amd64, nVidia GeForce FX5700,
Linux 2.6.8 x86_64 (SuSE 9.2), gcc 3.3.4, gdb 6.2.1,
cal3d, CS, cel cvs co 2005-02-26,
PS cvs update nearly daily.

Hope i can help,
Ralph.

[GlaDiaC]

Compile cal3d, CS, cel and planeshift with --enable-debug. Run the psclient with

gdb psclient

if it crashs type

bt full

in the gdb console.

help in gdb console and the manpage explains all your needs.

[GlaDiaC]

If you want a file, try this:

Code: [Select]

#!/bin/sh

export CRYSTAL=.
export CEL=.
export LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH

GDB=gdb
PLANESHIFT=psclient

ARGS=$*
PID=$$

cat > .dbgfile.$PID << HERE
file $PLANESHIFT
set args $ARGS
run
bt full
cont
quit
HERE

$GDB  -silent < .dbgfile.$PID &> gdb_log.$PID

rm -f .dbgfile.$PID
echo \"Log written to: gdb_log.$PID\"

code is not tested yet

[Xordan]

The biggest problem is that no programmer dev has a 64-bit PC to debug on

[Androgos]

Originally posted by Xordan
The biggest problem is that no programmer dev has a 64-bit PC to debug on

I would gladly take good hand of yours

The dump files is more or less just an non-exact BT (non because it shows the exact code location in HEX).

Console and GDB backtrace would be fine