Record Case Detail

This function is in beta test. Please help improve it in the issues here.

 pwd: /out/package
ppid: 349
   1: WRITELN echo 123 > 1.txt
   2: WRITELN echo 222 > 2.txt
   3: WRITELN echo 321 > 4.txt
   4: WRITELN cat < 1.txt 2.txt > 3.txt 4.txt
   5: WRITELN cat 1.txt
   6: WRITELN cat 2.txt
   7: WRITELN cat 3.txt
   8: WRITELN cat 4.txt
   9: WRITELN ls
  10: WRITELN exit

Your answer may be identical to the JOJ answer in the first several lines.

However, you will still get Wrong Answer because the complete output may be longer and there might be errors in the future lines.

Please double check your code to solve this problem and try again.

mumsh $ =================================================================
==350==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffc2c53c9b2 at pc 0x00000051a160 bp 0x7ffc2c532260 sp 0x7ffc2c532258
WRITE of size 1 at 0x7ffc2c53c9b2 thread T0
    #0 0x51a15f  (/out/package/mumsh_memory_check+0x51a15f)
    #1 0x5153dc  (/out/package/mumsh_memory_check+0x5153dc)
    #2 0x7f7f87f03b96  (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
    #3 0x41cce9  (/out/package/mumsh_memory_check+0x41cce9)

Address 0x7ffc2c53c9b2 is located in stack of thread T0 at offset 42706 in frame
    #0 0x5150bf  (/out/package/mumsh_memory_check+0x5150bf)

  This frame has 2 object(s):
    [32, 42440) 'pipes'
    [42704, 42706) 'line_input' <== Memory access at offset 42706 overflows this variable
HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext
      (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow (/out/package/mumsh_memory_chec

mumsh $ mumsh $ mumsh $ mumsh $ mumsh $ 123
mumsh $ 222
mumsh $ 222
321
mumsh $ 321
mumsh $ 1.txt
2.txt
3.txt
4.txt
driver
mumsh
mumsh_memory_check
mumsh $ exit

Notes

Stderr

Hints

Your Answer

JOJ Answer