On 02/01/2013 11:31 AM, Ludo Brands wrote: > > 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. As the program does two http requests just fine and fails on the third one (it alternatively does three very different pages and parameters and all fail, just because they are the third ), I think some more internal problem is more likely (buffer overflow or such). > strace is normal linux but will probably have to be installed or perhaps > even build from source. I'll take a look during the weekend. > 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. As the NAS with Optware installed, uses the harddisks for it's files, I have plenty of room. The system has 512 MB RAM. I don't know if it is configured to do swapping (I doubt it). > 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. I believe this is a 2 GHz ARM11. Should be fast enough. I'll take a look at LXDE. As the system is not Debian I can't (easily) use Debian packages by apt-get.- I already installed software (an old version of fpc) by extracting a dpkg manually. This worked, but resolving the dependencies manually is not fun.
The QNAP (with Optware) provides qpkg and ipkg packages. Maybe LXDE is available. > gdb and fpc work fine together. There are a few limitations but they are > also there when using gdb in lazarus. Nice ! I'll try to use this ASAP. > 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. Sounds good. > 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. > Thanks a lot for your help ! I'll be back on Monday. -Michael ------------------------------------------------------------------------------ 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
