On 03/28/2012 02:01 AM, Gilles Allard wrote: > On Wednesday 22 February 2012 10:32:43 Gilles Allard wrote: >> To debug a driver, I try to use Kgdb along with Gdb on a serial link >> between an host machine and the target one running the buggy driver. >> >> - Up to now, everything seems to be as expected. But if I try to continue >> target boot process using "monitor go", here is what I got ( and here is >> the problem ) : >> >> (gdb) monitor go >> go must execute on the entry cpu, please use "cpu -1" and then execute go >> (gdb) >> >> >From that point, I cannot do anything else but manually reset the target >>> and >> kill the Gdb session because of what seems to be an error message. >> So : is this a real bug or is there something wrong in the procedure I use >> ? > Hello to all of you. > > Does any one can help ? > I really need help for that problem; I really don't now what to do ! > I'll be grateful for any information ( suggestion, hint ... ).
You cannot use monitor commands for run control. If you are using gdb, you need to use the "continue" command and the gdb specific run control commands. I had intentionally disabled some features from the monitor pass through because they are not safe to use from the gdb context. Jason. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
