Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #43884

Re: Mecrisp 2.1.6 ARM Linux problem

From Paul Rubin <no.email@nospam.invalid>
Newsgroups comp.lang.forth
Subject Re: Mecrisp 2.1.6 ARM Linux problem
Date 2015-11-27 12:20 -0800
Organization A noiseless patient Spider
Message-ID <87io4nchz8.fsf@nightsong.com> (permalink)
References (1 earlier) <n36h7p$a6j$1@newsserver.rrzn.uni-hannover.de> <87d1uxdt6c.fsf@nightsong.com> <n36joc$atf$1@newsserver.rrzn.uni-hannover.de> <874mg9dr5j.fsf@nightsong.com> <n36mcs$bpe$1@newsserver.rrzn.uni-hannover.de>

Show all headers | View raw


Matthias Koch <matthias.koch@hot.uni-hannover.de> writes:
> You could use the disassembler to SEE the difference, but this would
> require to have the source code feed-in up and running first.

"SEE not found" -- maybe I have to load something for that?  I haven't
looked at the docs much yet, just played with the interpreter a little.

> * Copying in single lines one by one manually: Fine.
> * Copying in all lines at once manually: Crash with Illegal instruction.
> * Insert on standard input: Crash with Illegal instruction.
> Why ? It should be blocking, buffered IO... ?

Interesting observation.  One idea is a buffer overflow, where something
is reading the available chars and then handing them off to the
interpreter, which works ok when there's just a few chars.

I tried assembling with -g and running under gdb, but setting
breakpoints didn't work when I did the obvious thing.  I'll try some
more later.

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-25 23:40 -0800
  Re: Mecrisp 2.1.6 ARM Linux problem Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-11-26 09:54 +0100
    Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-26 01:08 -0800
      Re: Mecrisp 2.1.6 ARM Linux problem Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-11-26 10:37 +0100
        Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-26 01:52 -0800
          Re: Mecrisp 2.1.6 ARM Linux problem Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-11-26 11:22 +0100
            Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-27 12:20 -0800
              Re: Mecrisp 2.1.6 ARM Linux problem Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-12-09 15:04 +0100
                Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-12-09 23:50 -0800
                Re: Mecrisp 2.1.6 ARM Linux problem Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-12-10 12:00 +0100
  Re: Mecrisp 2.1.6 ARM Linux problem anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-26 09:27 +0000
    Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-27 01:06 +0100
      Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-27 18:35 +0100
        Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-27 10:24 -0800
          Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-27 23:27 +0100
        Re: Mecrisp 2.1.6 ARM Linux problem anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-28 11:19 +0000
          Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-28 17:44 +0100
      Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-28 22:19 -0800
        Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-29 20:47 +0100
          Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-29 12:13 -0800
            Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-30 01:37 +0100
              Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-29 19:20 -0800
                Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-30 23:29 +0100
                Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-11-30 18:06 -0800
                Re: Mecrisp 2.1.6 ARM Linux problem Bernd Paysan <bernd.paysan@gmx.de> - 2015-12-01 23:14 +0100
                Re: Mecrisp 2.1.6 ARM Linux problem Paul Rubin <no.email@nospam.invalid> - 2015-12-01 20:19 -0800

csiph-web