CompuServe Messages

It's been 11 days since your response (for which I thank you), so I should probably remind you what it was: > When your program is called the arguments are pointed to by a0. > Additionally the length of the argument is stored in d0. > What you need to do is copy using a dbra loop and then store a zero at the > end. I don't think you will get a linefeed if you do this. It isn't quite clear to me how this relates to my problem. You also say "you shouldn't rely on there being a terminator of any sort on the argument" but in fact it has never happened in my experience that there was not a <LF> there. Although I apparently once toyed with the idea of saving d0 at startup (I have a commented out move.l d0,… statement there which I removed when I sent it to you), I stayed with the method I learned from the sample programs that came with the CAPE assembler. For one thing, one has to parse the command line sooner or later anyway, if there might be more than one file listed, or flags… In any event, it's the way I coded the PD program JIStoJi, which I and others have been using for a couple of years, with no reports of problems reading a command line file. My original question was, why does it work fine when I use Devpac's Debug, but crash when I run it from the Devpac Edit screen? The main reason I bought Devpac was for the debugger, but if it is going to tell me that programs that compile with some kind of fault are OK, I'm better off going back to CAPE. The differences between the working CAPE-compiled program and the not-working Devpac-compiled program are 1) different include files 2) with CAPE I compile and link, with Devpac it's a one-step operation. The bug must be a result of one of those differences, but why won't the debugger tell me? Bart