<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/asm68c/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/asm68c/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/asm68c/discussion/</id><updated>2023-01-17T15:49:22.088000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>questions about asm68c software</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/9426f22d27/?limit=25#a153" rel="alternate"/><published>2023-01-17T15:49:22.088000Z</published><updated>2023-01-17T15:49:22.088000Z</updated><author><name>JOHN DIMEGLIO</name><uri>https://sourceforge.net/u/johnd007/</uri></author><id>https://sourceforge.net59e079d8299e1c71797acaae4efc3b6a465b0755</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I don't know, why would the asm68c 6800 assembler cause the software to go into a (not responding) mode or freeze up, when after initiating a compile of a 6800 assembly program? My email address: johndimeglio957@yahoo.com. Thank you.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Fig-forth double characters on typing from exorcism</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/941c245b4c/?limit=25#111a" rel="alternate"/><published>2022-09-17T06:03:57.271000Z</published><updated>2022-09-17T06:03:57.271000Z</updated><author><name>Richard Rothwell</name><uri>https://sourceforge.net/u/chergr/</uri></author><id>https://sourceforge.net0ddfa2dd239ad177d3ee346a5d7fef06d4cd1e36</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I can run figforth on the simulator fine. Except typing WORDS look like this.&lt;br/&gt;
WWOORRDDSS&lt;/p&gt;
&lt;p&gt;Typing backspace backspaces 5 characters.&lt;/p&gt;
&lt;p&gt;This does not occur in the exorsim monitor, so I figure its an issue with the forth and its adaption to call  EXBUG for EMIT and KEY. &lt;/p&gt;
&lt;p&gt;I have not diagnosed this properly yet, but though you might like to know,&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>strsave/mystrcpy</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/fb4cd4e7/?limit=25#5ade" rel="alternate"/><published>2018-09-15T13:56:18.035000Z</published><updated>2018-09-15T13:56:18.035000Z</updated><author><name>Joel Rees</name><uri>https://sourceforge.net/u/reiisi/</uri></author><id>https://sourceforge.netfa11facf6d5019a2e0f30f9412b5043bb441b0f0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Okay, I finally got the proper fix for this into the repository.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>strsave/mystrcpy</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/fb4cd4e7/?limit=25#ecd8" rel="alternate"/><published>2017-08-10T06:36:19.219000Z</published><updated>2017-08-10T06:36:19.219000Z</updated><author><name>Ron Yorston</name><uri>https://sourceforge.net/u/rmyorston/</uri></author><id>https://sourceforge.netc98f400153c59865af979cd5ee8bc6fdf3e701cf</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks for looking at this.&lt;/p&gt;
&lt;p&gt;On Fedora 26 I have gcc 7.1.1 and glibc 2.25.  It's a 64-bit system.&lt;/p&gt;
&lt;p&gt;I've now built and used the assembler on a 32-bit CentOS 6 system with gcc 4.4.7 and glibc 2.12.  In this case my source assembled without incident.  Clearly it's system-dependent.&lt;/p&gt;
&lt;p&gt;On both Fedora and CentOS Valgrind identifies the problem.  With my suggested change to the macro Valgrind doesn't report any runtime errors.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>strsave/mystrcpy</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/fb4cd4e7/?limit=25#73aa" rel="alternate"/><published>2017-08-09T23:54:45.449000Z</published><updated>2017-08-09T23:54:45.449000Z</updated><author><name>Joel Rees</name><uri>https://sourceforge.net/u/reiisi/</uri></author><id>https://sourceforge.netcfeb4ca4f595b52ed6ebf0deae0abef5cb5f76fa</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This is very odd. I don't see this behavior on my system -- Debian Wheezy, gcc 4.7.2 as of now. &lt;/p&gt;
&lt;p&gt;If you look at, say, fig-forth/fig-forth.list.goal, you should be able to see the results I get.&lt;/p&gt;
&lt;p&gt;I hope you'll be patient with me about this, because it would be a big favor if I could ask you to descend into the test-stuff directory and the fig-forth directory and do a make and make test in each of those, preferably with a fresh copy of the source, and tell me what the diffs say. &lt;/p&gt;
&lt;p&gt;And I've left this out of the tests in test-stuff/Makefile, but could you take a look at the output of assembling test-stuff/exptest.68c and tell me what you see?&lt;/p&gt;
&lt;p&gt;And could you tell me your version of gcc and/or clang?&lt;/p&gt;
&lt;p&gt;I do have a reason for that rather odd macro, but it will be easier to explain, and to figure out what I should do with the code once I have an idea what is actually happening there.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>strsave/mystrcpy</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/fb4cd4e7/?limit=25#e078" rel="alternate"/><published>2017-08-09T18:53:09.267000Z</published><updated>2017-08-09T18:53:09.267000Z</updated><author><name>Ron Yorston</name><uri>https://sourceforge.net/u/rmyorston/</uri></author><id>https://sourceforge.netc0fb9799fb152cd935ea97337f24968b106c8e33</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Here's a really, really basic source file:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="x"&gt;FLAG    EQU &lt;/span&gt;&lt;span class="p"&gt;$&lt;/span&gt;&lt;span class="nv"&gt;E084&lt;/span&gt;&lt;span class="x"&gt;&lt;/span&gt;
&lt;span class="x"&gt;FIRST   EQU &lt;/span&gt;&lt;span class="p"&gt;$&lt;/span&gt;&lt;span class="x"&gt;15CF&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;This produces output like:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;| 15cf:FIRST            || 15cf:FIRST           || e084:FLAG             |
| e084:FLAGa            |
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;where the second, duplicated symbols have a surplus character appended.  Sometimes printable, sometimes not.  And sometimes the assembler crashes without any output.  This is on Linux: Fedora 26.&lt;/p&gt;
&lt;p&gt;There's only one use of the macro &lt;code&gt;mystrcpy&lt;/code&gt;, in &lt;code&gt;strsave&lt;/code&gt;.   &lt;code&gt;length+1&lt;/code&gt; bytes are allocated for &lt;code&gt;newword&lt;/code&gt; and the macro is invoked as:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;mystrcpy(newword, oldword, length+1);
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;which expands to:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;(newword[length+1] = '\0', strncpy(newword, oldword, length+1-1));
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;So the null character is placed beyond the end of allocated memory.&lt;/p&gt;
&lt;p&gt;Changing the macro to have &lt;code&gt;dest[len-1]&lt;/code&gt; fixes the problem.  Though I'd be inclined to do away with the macro and revert to using &lt;code&gt;strcpy&lt;/code&gt;.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>strsave/mystrcpy</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/fb4cd4e7/?limit=25#4870" rel="alternate"/><published>2017-08-09T13:16:02.829000Z</published><updated>2017-08-09T13:16:02.829000Z</updated><author><name>Joel Rees</name><uri>https://sourceforge.net/u/reiisi/</uri></author><id>https://sourceforge.net6dcbb0ee43852d2cb0113c719ac2d163234573d6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks for giving the assembler a try.&lt;br/&gt;
My 6800 source code is not producing any writes beyond allocation.&lt;br/&gt;
Could you show some of your lines where this occurs, and describe the output you are getting?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>strsave/mystrcpy</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/fb4cd4e7/?limit=25#c68d" rel="alternate"/><published>2017-08-09T08:25:26.950000Z</published><updated>2017-08-09T08:25:26.950000Z</updated><author><name>Ron Yorston</name><uri>https://sourceforge.net/u/rmyorston/</uri></author><id>https://sourceforge.nete350799d999a2667f15baa8b562606816bb9a059</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks for releasing this assembler.&lt;/p&gt;
&lt;p&gt;I tried it with some of my 1983-vintage code and found a problem:  when the mystrcpy macro pre-terminates the new string it writes beyond the end of the allocated buffer.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Getting started.</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/1f971ac8/" rel="alternate"/><published>2012-11-03T05:40:32.960000Z</published><updated>2012-11-03T05:40:32.960000Z</updated><author><name>Joel Rees</name><uri>https://sourceforge.net/u/reiisi/</uri></author><id>https://sourceforge.net3ecbccb15df6743928d7765ab69ec7215ea95fcf</id><summary type="html">I've been playing with the [exorsim](http://exorsim.sourceforge.net/) project.

I've succeeded in single-stepping through some simple assembler output using the simulator in monitor mode, without either MDOS or Flex.

~~~~~~~~~~
exor --mon
~~~~~~~~~~

jumps directly to the monitor.

Use the paper tape load ("l") command to load the S1-S9 output. (See the usage page for the project for the monitor commands.)

What you do here is pull the S1-S9 object into a text editor. (It's all ASCII hex, so there are no problems pulling it into an ordinary text editor.) Select-all in the text editor and copy. 

~~~~~~~~~~~~~
./exor --mon 
~~~~~~~~~~~~~

in a shell, in the directory where you made the exorsim object. It should give you a "%" prompt.

At the "%" prompt, paste (right-click, not ctl-v) the S1-S9 output into the simulator session. At the next load prompt, hit ctl-C.

If you haven't yet used the "h" command to read the list of monitor/debugger commands, do so now. The single-step command is "s". 

(You may want to play with the monitor/debugger before you try single-stepping anything really big.)</summary></entry><entry><title>Getting started.</title><link href="https://sourceforge.net/p/asm68c/discussion/1187460/thread/1f971ac8/" rel="alternate"/><published>2012-10-08T13:28:35.994000Z</published><updated>2012-10-08T13:28:35.994000Z</updated><author><name>Joel Rees</name><uri>https://sourceforge.net/u/reiisi/</uri></author><id>https://sourceforge.netac11b590d0e45a6de5c59160ded5f5cd5007f92f</id><summary type="html">The latest tarball is theoretically the most tested and bug-free.</summary></entry></feed>