[lazarus] *BSD problems with Lazarus

[Marc Weustink]

+ -----Original Message-----
+ From: Marco van de Voort [mailto:marcov at Stack.nl]
+ Sent: donderdag 19 juni 2003 17:52
+
+ > + I debugged Lazarus and Pipe, and found the problem.
+ > +
+ > + The syscall pipe returns the filedescriptors in registers,
+ > + and then some C macro copies it to the int[2] structure.
+ > + I haven't seen this in the initial port I guess.
+ >
+ > ??? I've read that some incarnations (free, open, or net) of BSD return
+ > syscal params by stack
+
+ Not that I know of ;-)
+
+ They usually pass all params except sysnr on the stack, but return
+ values are registers.

Eehh... you're right.

BTW, are we the first using pipes in BSD ?

+ > + I quick checked, and NetBSD also does this, on all
+ > + (processor) platforms.
+ > +
+ > + The FreeBSD fix is commited, the NetBSD/i386 will follow tomorrow or
+ > + saturday.
+ > +
+ > + ----
+ > + I do see this now in the output, but the debugged program starts up:
+ > + (notice the warning)
+ > +
+ > + [snip
+ > + [Debugger] Console output: ~"/fpc/lazproj/project1' has changed;
+ > + re-reading symbols.\n"
+ > + [WARNING] Debugger: Unknown stopped reason:
+ > + TCmdLineDebugger.SendCmdLn "info program"
+ > + [Debugger] Log output: &"info program\n"
+ > + [Debugger] Target PID: 83914
+ > + TCmdLineDebugger.SendCmdLn "-exec-continue"
+ >
+ > Have you enabled the "generate debug info" compiler option ?
+
+ Now I have, but there hasn't changed much. Everything seems to work,
+ but I still get that [WARNING]

Ah, *that* one, yes there is one warning which isn't a warning (It's is the
result of my initial tbreak, to allow stepping). You can ignore that one.

Marc