mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ruben Louw <lfxciii@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Subject: Re: [ptxdist] Gdb debugging helper
Date: Fri, 11 Jan 2013 10:47:07 +0200	[thread overview]
Message-ID: <CAOP6b3j0z+crcNE22PCEjZZ0du9w+jJeaRLRaGQO76F6R1Uh2A@mail.gmail.com> (raw)
In-Reply-To: <201301110940.10949.jbe@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 1846 bytes --]

hmm. makes sense to be on host. But I think this should be included when
build the toolchain or something, I'm only speculating. but i'll play
around with it, hopefully smoke does'nt come out anywhere.

Cheers!

Ruben

On Fri, Jan 11, 2013 at 10:40 AM, Juergen Beisert <jbe@pengutronix.de>wrote:

> Hi Ruben,
>
> Ruben Louw wrote:
> > > ("Computer! Find the bugs in my app right now!"?) ;)
> >
> > hehehe, I wish it was this simple.
>
> Maybe we should give it a try :))
>
> > The debugging helper enables the viewing of complex objects in the IDE
> (Qt
> > Creator in my case). so when gdbserver is started on the target, the IDE
> > then starts gdb on the host and the to communicate with each other. As
> soon
> > as a break point is reached, the variable types and values are displayed
> > using a debug helper. from what I could gather, this helper is either
> > python or normal c++.
>
> Hmm, then these helpers should run on your host. So, PTXdist and your
> target's
> gdbserver are not involved. When these helpers are using the gdb to collect
> the information they need, I would guess it should work out of the box.
>
> >> Please keep always in mind the difference between your target and your
> >> host. Most of the time, only the small gdbserver runs >on your target
> and
> >> the main full blown/featured debugger on your host.
> >
> > this is also how I understand it, all the helper does is "Indetify" the
> > types and its values, then you dont have to guess what the content of the
> > variable or objects are.
>
> I know this behaviour from DDD where you also can click through linked
> lists
> and so on. Very comfortable.
>
> Happy hacking.
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K.                              | Juergen Beisert
>   |
> Linux Solutions for Science and Industry      | http://www.pengutronix.de/ |
>

[-- Attachment #1.2: Type: text/html, Size: 2523 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-11  9:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11  7:30 Ruben Louw
2013-01-11  8:09 ` Juergen Beisert
2013-01-11  8:22   ` Ruben Louw
2013-01-11  8:40     ` Juergen Beisert
2013-01-11  8:47       ` Ruben Louw [this message]
2013-01-11  9:42         ` Michael Olbrich
2013-01-11 10:58           ` Ruben Louw
2013-01-11  9:42         ` [ptxdist] Gdb debugging helper [PATCH] Tim Sander
2013-01-11 10:57           ` Ruben Louw
2013-01-11 12:27             ` Tim Sander
2013-01-11 12:30               ` Ruben Louw
2013-01-11 12:45                 ` Juergen Beisert
2013-01-11 12:57                   ` Ruben Louw
2013-01-11 13:12                     ` Juergen Beisert
2013-01-11 13:16                       ` Ruben Louw
2013-01-11 13:25                         ` Juergen Beisert
2013-01-11 13:33                           ` Ruben Louw
2013-01-11 13:39                             ` Ruben Louw
2013-01-11 13:49                             ` Juergen Beisert
2013-01-11 12:30             ` Michael Olbrich
2013-01-11 12:37               ` Ruben Louw
2013-01-11 12:42                 ` Ruben Louw
2013-01-11 13:00                 ` Michael Olbrich
2013-01-11 13:02                   ` Ruben Louw
2013-01-11 13:18                     ` Michael Olbrich
2013-01-11 13:20                       ` Ruben Louw
2013-01-11 13:21                         ` Ruben Louw
2013-01-11 13:24               ` Tim Sander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOP6b3j0z+crcNE22PCEjZZ0du9w+jJeaRLRaGQO76F6R1Uh2A@mail.gmail.com \
    --to=lfxciii@gmail.com \
    --cc=jbe@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox