I am still struggling with a service that either will start and immediately stop, or will run but appears unable to listen on port 8080. Usually with things like this, I simply litter code with some type of tracing (often OutputDebugString() calls on Windows), and try to bracket the problem. This seems like a good candidate for it, because attaching a debugger to Squeak (particuarly for the case in which it won't stay running) sounds like a LOT more trouble than printing "got this far" messages until I know where it quits.
-log: has not been much help. Is there something similar to the change or error logs that might be appropriate to use?
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029
Why not just use OutputDebugString?
Smalltalk>>outputDebugString: aString <apicall: void 'OutputDebugStringA' (char*) module: 'kernel32.dll'>
Cheers, - Andreas
Bill Schwab wrote:
I am still struggling with a service that either will start and immediately stop, or will run but appears unable to listen on port 8080. Usually with things like this, I simply litter code with some type of tracing (often OutputDebugString() calls on Windows), and try to bracket the problem. This seems like a good candidate for it, because attaching a debugger to Squeak (particuarly for the case in which it won't stay running) sounds like a LOT more trouble than printing "got this far" messages until I know where it quits.
-log: has not been much help. Is there something similar to the change or error logs that might be appropriate to use?
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029
Bill Schwab wrote:
I am still struggling with a service that either will start and immediately stop, or will run but appears unable to listen on port 8080. Usually with things like this, I simply litter code with some type of tracing (often OutputDebugString() calls on Windows), and try to bracket the problem. This seems like a good candidate for it, because attaching a debugger to Squeak (particuarly for the case in which it won't stay running) sounds like a LOT more trouble than printing "got this far" messages until I know where it quits.
-log: has not been much help. Is there something similar to the change or error logs that might be appropriate to use?
Bill
The Logging package was developed with this in mind, it uses SimpleLog or Toothpick as a back end.
I am not sure what support either of those have for windows debugging/tracing. They support Syslog and logging to files. SimpleLog also supports log rotation.
Keith
squeak-dev@lists.squeakfoundation.org