> On Oct. 3, 2016, 12:06 p.m., Andreas Sandberg wrote: > > Wouldn't it make more sense to just disallow multiple GDB clients to be > > attached at the same time? > > Alexandru Dutu wrote: > This does not make sense to me as one can run a configuration with > multiple, different processes. For example: threadContext A will be executing > process 1 and threadContext B will be executing process 2. In this case 2 gdb > listeners will be instantiated and each will be listening on a different > port. Imho, having multiple GDB clients is a neat feature.
Right, I see what you mean. Just ignore me. :) - Andreas ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3635/#review8757 ----------------------------------------------------------- On Oct. 3, 2016, 6:41 a.m., Alexandru Dutu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3635/ > ----------------------------------------------------------- > > (Updated Oct. 3, 2016, 6:41 a.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 11654:5cc5f694f938 > --------------------------- > gdb: Adds a warning in case gdb is attached multiple times > Instead of scheduling another event, this patch adds a warning in case gdb > is attached multiple times and the first attachement event has not been > processed yet. > > > Diffs > ----- > > src/base/remote_gdb.cc 2c111e634da005e2b78981fadd0368662454f2ed > > Diff: http://reviews.gem5.org/r/3635/diff/ > > > Testing > ------- > > Regressions pass. > > > Thanks, > > Alexandru Dutu > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
