Hi Sebastian

 >> Another problem with the buffer in emcrsh is that it seams to be
 >> rather small, just big enough for a few hundred commands. Once this
 >> buffer runs over emcrsh terminates.
 >
 > Ugh, that doesn't sound right.
 >
 > Could you open a bug in the sourceforge bug tracker for this please?

I'm not sure that it's an error or just a small buffer and I misuse emcrsh.

The buffer holds abut 124 line like this one (about 5.5 kB in total):

   set mdi g1x0.0123123y1.123123z2.123123f1234

But the buffer overflow is not handled by emcrsh. it crashes and 
displays this:


  *** buffer overflow detected ***: emcrsh terminated
  ======= Backtrace: =========
  /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0x2e8390]
  /lib/tls/i686/cmov/libc.so.6(+0xe12ca)[0x2e72ca]
  /lib/tls/i686/cmov/libc.so.6(+0xe05fa)[0x2e65fa]
  emcrsh[0x804e0ed]
  /lib/tls/i686/cmov/libpthread.so.0(+0x596e)[0x83b96e]
  /lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0x2d3a4e]
  ======= Memory map: ========
  00110000-001f9000 r-xp 00000000 08:01 797977 
/usr/lib/libstdc++.so.6.0.13
  001f9000-001fa000 ---p 000e9000 08:01 797977 
/usr/lib/libstdc++.so.6.0.13
  001fa000-001fe000 r--p 000e9000 08:01 797977 
/usr/lib/libstdc++.so.6.0.13
  001fe000-001ff000 rw-p 000ed000 08:01 797977 
/usr/lib/libstdc++.so.6.0.13
  001ff000-00206000 rw-p 00000000 00:00 0
  00206000-00359000 r-xp 00000000 08:01 786494 
/lib/tls/i686/cmov/libc-2.11.1.so
  00359000-0035a000 ---p 00153000 08:01 786494 
/lib/tls/i686/cmov/libc-2.11.1.so
  0035a000-0035c000 r--p 00153000 08:01 786494 
/lib/tls/i686/cmov/libc-2.11.1.so
  0035c000-0035d000 rw-p 00155000 08:01 786494 
/lib/tls/i686/cmov/libc-2.11.1.so
  0035d000-00360000 rw-p 00000000 00:00 0
  00645000-00660000 r-xp 00000000 08:01 790839     /lib/ld-2.11.1.so
  00660000-00661000 r--p 0001a000 08:01 790839     /lib/ld-2.11.1.so
  00661000-00662000 rw-p 0001b000 08:01 790839     /lib/ld-2.11.1.so
  00708000-00750000 r-xp 00000000 08:01 787236     /usr/lib/libnml.so.0
  00750000-00751000 r--p 00047000 08:01 787236     /usr/lib/libnml.so.0
  00751000-00752000 rw-p 00048000 08:01 787236     /usr/lib/libnml.so.0
  00752000-00753000 rw-p 00000000 00:00 0
  00836000-0084b000 r-xp 00000000 08:01 786606 
/lib/tls/i686/cmov/libpthread-2.11.1.so
  0084b000-0084c000 r--p 00014000 08:01 786606 
/lib/tls/i686/cmov/libpthread-2.11.1.so
  0084c000-0084d000 rw-p 00015000 08:01 786606 
/lib/tls/i686/cmov/libpthread-2.11.1.so
  0084d000-0084f000 rw-p 00000000 00:00 0
  009e6000-00a0a000 r-xp 00000000 08:01 786547 
/lib/tls/i686/cmov/libm-2.11.1.so
  00a0a000-00a0b000 r--p 00023000 08:01 786547 
/lib/tls/i686/cmov/libm-2.11.1.so
  00a0b000-00a0c000 rw-p 00024000 08:01 786547 
/lib/tls/i686/cmov/libm-2.11.1.so
  00a76000-00a79000 r-xp 00000000 08:01 787230     /usr/lib/libemcini.so.0
  00a79000-00a7a000 r--p 00002000 08:01 787230     /usr/lib/libemcini.so.0
  00a7a000-00a7b000 rw-p 00003000 08:01 787230     /usr/lib/libemcini.so.0
  00ab2000-00ab3000 r-xp 00000000 00:00 0          [vdso]
  00d5e000-00d7b000 r-xp 00000000 08:01 786529     /lib/libgcc_s.so.1
  00d7b000-00d7c000 r--p 0001c000 08:01 786529     /lib/libgcc_s.so.1
  00d7c000-00d7d000 rw-p 0001d000 08:01 786529     /lib/libgcc_s.so.1
  08048000-0805a000 r-xp 00000000 08:01 787287     /usr/bin/emcrsh
  0805a000-0805b000 r--p 00012000 08:01 787287     /usr/bin/emcrsh
  0805b000-0805c000 rw-p 00013000 08:01 787287     /usr/bin/emcrsh
  09f88000-09fa9000 rw-p 00000000 00:00 0          [heap]
  b70c5000-b70c6000 ---p 00000000 00:00 0
  b70c6000-b78c9000 rw-p 00000000 00:00 0
  b78d0000-b78d1000 rw-p 00000000 00:00 0
  b78d1000-b78d3000 rw-s 00000000 00:04 557070     /SYSV000003eb (deleted)
  b78d3000-b78d7000 rw-s 00000000 00:04 524301     /SYSV000003ea (deleted)
  b78d7000-b78d9000 rw-s 00000000 00:04 491532     /SYSV000003e9 (deleted)
  b78d9000-b78db000 rw-p 00000000 00:00 0
  bfaa0000-bfab5000 rw-p 00000000 00:00 0          [stack]
  Aborted


Bug or not? I guess emcrsh should handle the buffer overflow and prevent 
the reported buffer overflow in libc, so it's bug, right?

See you
Flo


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to