My guess would be the USA :-)

Michael.

Well, I may find more time for Lazarus development. My employer decided it was time to part ways... but I got a nice severance package so I have about 3 months of float before I have to work again.

So, I'm now officially an independant technology consultant, until a new job I'm waiting on becomes available, which might be a few months.

So far I'm working about 3 hours a day and making more than at my previous job, so it's working out. In fact if it keeps up this well who knows, maybe I'll stick with it full time.

Anyway, wish me luck, and if anyone is a consultant and has any tips for me regarding finding new business, I'm all ears!

Tony Maro

http://www.maro.net/

+ From: Marco van de Voort
+ Sent: donderdag 19 juni 2003 17:20
+
+ 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 retun syscal params by stack

+ 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 ?

Marc

+ -----Original Message-----
+ From: Marco van de Voort
+ 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

You win the cigar! Alabama to be exact.

But regardless, I was fishing for more generic info than regional.

Thanks,
Tony

Not that I know of ;-)

They usually pass all params except sysnr on the stack, but return values are registers.

Now I have, but there hasn't changed much. Everything seems to work, but I still get that [WARNING]

It would help if we knew what country you are in.

Ian

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 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"