[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Simulavr-devel] Connect with gdb to a core of a python simulation
From: |
Marek Pietrzak |
Subject: |
Re: [Simulavr-devel] Connect with gdb to a core of a python simulation |
Date: |
Wed, 17 Aug 2011 23:49:05 +0200 |
I'm afraid Petr is right and current design doesn't support multiple gdb
servers, or I do something wrong, anyway multiple instances for me lock
one other. I have to check in the code how it should be configured.
Single core should be ok though. I can also imagine having a single gdb
instance and cores as multiple threads in the execution.
The patches:
patch for src/python/pysimulavr.i
@@ -30,6 +30,7 @@
#include "atmega668base.h"
#include "atmega16_32.h"
#include "attiny2313.h"
+ #include "gdb.h"
%}
@@ -166,4 +167,6 @@
%include "atmega16_32.h"
%include "attiny2313.h"
+%include "gdb.h"
+
// EOF
and for src/Makefile.am
@@ -29,7 +29,7 @@
if PYTHON_USE
address@hidden@
-PYTHON_XTRA_INC=-Ipython
+PYTHON_XTRA_INC=-Ipython -Icmd
PYTHON_MODUL_INTERFACE=$(srcdir)/python/pysimulavr.i
noinst_LTLIBRARIES += lib_pysimulavr.la
nodist_lib_pysimulavr_la_SOURCES=pysimulavr_wrap.cpp
On Wed, 2011-08-17 at 21:21 +0200, Sebastian wrote:
> I am.
>
> With this change, is it only possible to connect to one core of a
> multicore simulation (the interface supports assigning gdb-ports to
> devices but the implementation has some global state), or was the
> following statement wrong?
>
> Am Montag, den 15.08.2011, 22:34 +0200 schrieb Petr Hluzín:
> > You cannot simulate multiple AVR chips with GDB because our GDB
> > processing code does not support multiple processes and we cannot
> > pretend multiple GDB servers now.
>
>
>
> _______________________________________________
> Simulavr-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/simulavr-devel
Re: [Simulavr-devel] Connect with gdb to a core of a python simulation, ThomasK, 2011/08/18