[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] multicore debugging
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of pvuser pvuser
> Sent: Monday, May 27, 2013 10:50 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] multicore debugging
>
> Hi,
>
> I would have some questions regarding the current Eclipse
> support for multicore debugging:
>
> 1) How can I represent cores in Eclipse? Can I use thread
> groups or threads? Can I represent each core as a thread? How
> Eclipse knows of the existence of multiple cores?
Open-source CDT does not yet represent cores as their own
entity in the Debug view. However, some products based
on CDT do that already.
>From what I have been told, some people re-use the concept
of GDB threads to represent cores. That should work
with CDT.
We plan on adding this support to CDT in the future.
> I have a single binary file that contains code for multiple
> cores. Each core should run its code independently of other cores.
>
> In the GDB MI protocol, all commands that are thread-specific
> have an additional thread identifier option (--thread,
> --frame). There is also mentioned the "core" field, in the
> async record:
> *stopped,reason="reason",thread-id="id",stopped-threads="stopp
> ed",core="core".
> - Is there support in Eclipse for the "core" field?
At this time we use the 'core' field in:
- the Debug view, where we should where add text to indicate
on which core a thread/process runs.
- to support the multicore visualizer
http://wiki.eclipse.org/CDT/User/NewIn81#Multicore_Visualizer_View
> 2) GDB non-stop mode: it is possible to examine the state of
> one thread, while other threads are running
> - Is there support in Eclipse for this mode?
Yes.
http://wiki.eclipse.org/CDT/User/FAQ#What_is_the_difference_between_Non-stop_and_All-stop_multi-threaded_debugging.3F
> 3) Elf Binary Parser
> - How difficult would be to extend the Elf Binary Parser
> in order to be able to support a custom binary executable
> that contains debug information for multiple cores?
I'm not knowledgeable about that.
Maybe someone else?
> 4) What about variable/register/memory Views? How are these
> handled in multicore context?
When you select a thread in the Debug view, those views are
automatically updated to show the content for that thread.
Since a thread runs on a specific core, those views work
automatically.
I hope this helps.
Marc