On 02/01/2013 09:43 AM, Michael Schnell wrote: > > I see. What "OS" properties exactly might trigger such behavior ? Kernel > version, libraries, ... ? > Basically the consts and structures you find in the fpc units sockets and termio and their include files. These are the fpc bindings and the definitions should match the header files for your OS. Is the OS this one: http://sourceforge.net/projects/qosgpl/ ? This seems to be standard linux.
>> Can you make an strace of your program? > I need to look up what "strace" is. But if this is some normal Linux > tool I think I will be able to do it. > strace is normal linux but will probably have to be installed or perhaps even build from source. > Unfortunately up till now, I don't know how I could be able to run an > fpc program in some kind of debugger on the headless box.. > > Possible alternatives could be: > - Install some kind of widget set (qt ?) and some kind of remote X > server (VNC ?) and compile Lazarus on the system and access it via this > remote GUI via SSH. (Sounds like a really huge task :-( ) You need quite some memory to build lazarus on the system. The ARM debian machine I'm using is a cheepo android 7" netbook that boots into Debian on a 2GB SDCard. It leaves debian with 220M to work with. I need another 200MB of swap (external USB stick) to build lazarus. LXDE is installed on it and it allows me to ssh in it with X forwarding. Speed is not terrible but debugging in lazarus works fine. > - Install a gdb stub on the box and do remote debugging via SSH with > Lazarus on a PC. (Seemingly nobody ever tried to do remote debugging > with Lazarus :-( ) > - Use the command line debugger on the box via SSH. (I never used the > command line debugger yet, (besides some initial tests on simple C > programs) and I don't know if pure gdb can decently work with fpc > programs :-( ) > gdb and fpc work fine together. There are a few limitations but they are also there when using gdb in lazarus. Compared to installing lazarus on the box, this is definitely the easiest solution. The use of gdb and fpc is not that different from gdb and C. When looking up addresses you need to be aware that fpc has its own name mangling. As in C, gdb is also case sensitive for address lookups with fpc. > So three times :-( :-( :-( here. > > What I will do in the weekend is activate the soc "Monitor" callback and > do some tracing with same... > >> That would give more insight in where things are going wrong. A >> tcpdump would be helpful also. > I need to look up what "tcpdump" is. But if this is some normal Linux > tool I think I will be able to do it. >> The information you gave us doesn't give a lot to go by. > I did suppose that and I'm grateful for the instructions on what I need > to provide additionally to help finding the problem. > Try to get the strace and tcpdump first before starting to debug fpc code. Just by looking at these data and at the synapse/fpc code we can probably find out where things are going wrong. Use strace with -tt to get timing information in the trace. Ludo ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
