Re: [Qemu-devel] [PATCH v2] Add the -semihosting-config option.

2014-11-20 Thread Peter Maydell
On 19 November 2014 10:31, Peter Maydell peter.mayd...@linaro.org wrote: On 18 November 2014 20:19, Liviu Ionescu i...@livius.net wrote: The usual semihosting behaviour is to process the system calls locally and return; unfortuantelly the initial implementation dinamically changed the target

Re: [Qemu-devel] [PATCH v2] Add the -semihosting-config option.

2014-11-20 Thread Liviu Ionescu
On 20 Nov 2014, at 17:22, Peter Maydell peter.mayd...@linaro.org wrote: ... I had to move the declaration and definition of semihosting_target to gdbstub.h and gdbstub.c, because otherwise the linux-user targets won't compile. (They don't compile vl.c.) :-( please let me know when the

Re: [Qemu-devel] [PATCH v2] Add the -semihosting-config option.

2014-11-20 Thread Peter Maydell
On 20 November 2014 15:35, Liviu Ionescu i...@livius.net wrote: On 20 Nov 2014, at 17:22, Peter Maydell peter.mayd...@linaro.org wrote: ... I had to move the declaration and definition of semihosting_target to gdbstub.h and gdbstub.c, because otherwise the linux-user targets won't compile.

Re: [Qemu-devel] [PATCH v2] Add the -semihosting-config option.

2014-11-19 Thread Peter Maydell
On 18 November 2014 20:19, Liviu Ionescu i...@livius.net wrote: The usual semihosting behaviour is to process the system calls locally and return; unfortuantelly the initial implementation dinamically changed the target to GDB during debug sessions, which, for the usual arm-none-eabi-gdb, is

[Qemu-devel] [PATCH v2] Add the -semihosting-config option.

2014-11-18 Thread Liviu Ionescu
The usual semihosting behaviour is to process the system calls locally and return; unfortuantelly the initial implementation dinamically changed the target to GDB during debug sessions, which, for the usual arm-none-eabi-gdb, is not implemented. The result was that during debug sessions the