On 2009-5-18 7:42, Dave Korn wrote:
Lenik wrote:
Are you sure you don't have some competing tools getting in the way of
proper cygwin operation?
No, I've set PATH to cygwin/bin only, before execute expr.
Doesn't necessarily mean there aren't system-wide hooks being loaded into
every application running.
This is hard to say, but I think my system is ok, all tools in coreutils
except expr are ok to run.
stackdump added.
Can you get this to reproduce under GDB? A backtrace from the exception
caught there, plus the output from "info files", would tell us more. From the
tiny bit of stackdump it managed to output before crashing, it does look like
either the stack is very corrupted, or the program counter ended up in a
rather unexpected area of memory owing to some intercepting DLL or similar.
I don't know how to do in detail, this is what I get, I don't have debug
symbols.
(gdb) run
Starting program: /usr/bin/expr
[New thread 3988.0xd84]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New thread 3988.0x9f4]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
0x05240000 in ?? ()
(gdb)
Thanks,
Lenik
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
