Hello,

I am trying to get back up to speed after a couple of years away from FPC/Laz, and I hope I am not a P.I.T.A. ...

I searched the mail archive, but I found nothing.

I am using 'fpc 2.7.1', and debugserver does not compile/make for me.

Did I overlook a setting?

Thank you.

This is the output of make:
$ make
/usr/lib/codetyphon/fpc/bin/i386-linux/ppc386 -Fu../../rtl -FE.
-FUunits/i386-linux -di386 msgintf.pp
/usr/lib/codetyphon/fpc/bin/i386-linux/ppc386 -Fu../../rtl -FE.
-FUunits/i386-linux -di386 debugserverintf
debugserverintf.pp(116,18) Error: Identifier not found "Socket"
debugserverintf.pp(122,3) Warning: Symbol "Str2UnixSockAddr" is deprecated
debugserverintf.pp(123,10) Error: Wrong number of parameters specified
for call to "Bind"
debugserverintf.pp(125,17) Error: Identifier not found "Listen"
debugserverintf.pp(165,18) Error: Identifier not found "Socket"
debugserverintf.pp(171,13) Warning: Symbol "family" is deprecated
debugserverintf.pp(173,13) Warning: Symbol "port" is deprecated
debugserverintf.pp(174,13) Warning: Symbol "addr" is deprecated
debugserverintf.pp(175,10) Error: Wrong number of parameters specified
for call to "Bind"
debugserverintf.pp(176,48) Warning: Local variable "FFileName" does not
seem to be initialized
debugserverintf.pp(177,17) Error: Identifier not found "Listen"
debugserverintf.pp(244,13) Error: Wrong number of parameters specified
for call to "Accept"
debugserverintf.pp(283,11) Error: Identifier not found "ShutDown"
debugserverintf.pp(381) Fatal: There were 8 errors compiling module,
stopping
Fatal: Compilation aborted
make: *** [debugserverintf.ppu] Error 1

After more searching I found some posts that seem to indicate that the debugserver has not worked for some time. One of those posts lead me to the debugserver server that is an example in fpGUI. I built that and it works. tiOPF was also suggested. I intend to look into it as well.

bsquared wrote

the debugserver server that is an example in fpGUI. I built that and it works. tiOPF was also suggested. I intend to look into it as well.

I use both of those. Just a small note that the tiOPF logging has a few more convenience LogValue() etc methods, and can also log to the debug server too.

Regards,
- Graeme -

Hmm, just a suggestion:

Change all calls to (I don't know if argument lists are the same, it's been a long time)
Listen() to fpListen()
ShutDown() to fpShutDown()
Socket to fpSocket()
Bind() to fpBind()

Prefix symbols:
Family, port and addr symbols with `sin_`

Make sure that unit sockets is used (normally not a problem). If there are any other problems, the sort of `wrong number of arguments` or `wrong argument type`, post them and the associated code, I have a working TCPserver here which compiles on 2.6, so I'm sure I can lookup the calls and "translate" them.

I think the cause of the issue is that Listen(), Bind(), etc... where the previous name of the calls. Most changed to something prefixed with `fp`.

Note that I can not guarantee that the modified code will work, as there are probably other incompatibilities lingering around somewhere.

Good luck :-)

Thank you I will give that a try.

If I recall correctly you don't use Laz much; however, is it possible that it could log to Laz messages window?

Thank you.

In our previous episode, Ewald said:

http://wiki.freepascal.org/User_Changes_2.4.0#Almost_all_old_1.0.x_socket_unit_functions_have_been_removed

Some argument types changed from formal type to pointer, and return values changes from boolean to integer.

The description of the fp* function typically matches the one in socket tutorials and man pages. The deprecated ones where FPC specific, specially wrt returnvalues and errorhandling.

bsquared wrote

If I recall correctly you don't use Laz much; however, is it possible that it could log to Laz messages window?

I don't think so. Don't think you can log to message debugger has an event window. You can set breakpoints, that do not stop. And they can log to dbg event window, including evaluating ONE expression (watch). They can alos take a snapshot of all watches and top 5 stack frames (history window)

Yep, that about says it :-) I didn't know it was actually documented though...

I like the tiOPF based Logging. Nice work.

bsquared wrote

If I recall correctly you don't use Laz much; however, is it possible that it could log to Laz messages window?

As Martin mentioned, I don't think you can log to the Laz messages window - it just captures FPC output.

Regards,
- Graeme -

bsquared wrote

I like the tiOPF based Logging. Nice work.

It is the most reliable logging framework I know. For example, the dbugintf unit in FPC has major issues when used under Windows. If you generate many messages per second (which happens easily when you debug Visitor classes in tiOPF), lost of those messages simply get lost and never display in the debug server. This doesn't seem to happen under Linux though.

But with the tiOPF logging you get consistent logging on all platforms, even if you use its own Visual Log Window, or Log File etc. The message are never lost because the tiOPF can buffer the log items.

I would still like to extend that to debug whole classes or more complex data types - something like what CodeSite does. If only I had more free time. :-/

Regards,
- Graeme -

It's difficult to compare the 2 kinds of logging.

dbugintf sends the logs to a separate process. tiLog is inside the running application. The former can be used to collect logs from several CGI processes, the latter currently cannot handle this (to my knowledge).

That said, I am aware of the windows problem, but have till now not yet found the cause of the problem. Since I use dbugintf exclusively on Linux, I haven't experienced problems yet.

I am open for suggestions to fixing the problem, though.

Michael.

That said, I am aware of the windows problem, but have till now not yet found the cause of the problem.

I too have tried to find the problem, but couldn't spot the issue.

G.

I am on linux as well. What are you using for dbugsrv?

Hi bsquared,

Just as an aside, the debug server included in the lazarus tools directory compiles fine for me. If you want a GUI version, you can use that one out of the box.

Thank you,
Noah Silva
2012/11/08 2:26 "bsquared" :

Thanks. I did not see that one.