After coming across this stackoverflow post: http://stackoverflow.com/questions/913912/bash-shell-for-windows
I discovered Console: http://sourceforge.net/projects/console
And I can use it with the Git shell, setting the shell to:
"C:\Program Files (x86)\Git\bin\sh.exe" --login -iJust amazing!
Update 2017/05/04: The original project is no longer active, but this fork seems to be: https://github.com/cbucher/console
Recently I needed to see when my threads were executing and in which processor, and
it took me a couple of days to get this done. Here is the best solution I’ve found.
First of all, we need the kernel to be compiled with some debug features enabled
http://www.mjmwired.net/kernel/Documentation/trace/ftrace.txt
https://www.kernel.org/doc/Documentation/trace/ftrace.txt
We’ll need to mount the debugfs
mount -t debugfs nodev /sys/kernel/debug
There is a front-end to the ftrace which is the trace-cmd command. It will enable the debugging features, start the tracing, and disable afterwards, and it can be really simple to use:
# trace-cmd start -e "sched:sched_switch" ./program_to_trace
After that you can use the KernelShark app to read the trace.dat file. Or you can convert it to VCD using:
# trace-cmd report > trace.txt # sched_switch2vcd trace.txt trace.vcd
The sched_switch2vcd app is available here: https://github.com/rsvargas/sched_switch2vcd . I like to use gtkwave to visualize the data.
Update in 2015/07/08:
After wasting a couple hours I’ve found someone who had the solution, which I found through this guy’s blog.
In my case, what I had was a chroot jail inside a server (which I also had full control), here are the steps:
# xauth list devserver/unix:10 MIT-MAGIC-COOKIE-1 f44098e4ee6687e163c152a72c7dacbd
and copy the auth data;
# xauth add devserver/unix:10 MIT-MAGIC-COOKIE-1 f44098e4ee6687e163c152a72c7dacbd