From: "james osburn" <jjosburn@hotmail.com>
To: gdb@sources.redhat.com
Subject: Re: tracing ( was Re: what are gdbstubs?)
Date: Thu, 24 Mar 2005 23:48:00 -0000 [thread overview]
Message-ID: <BAY13-F4029FB867B3C92AF7B57ACD8400@phx.gbl> (raw)
In-Reply-To: <424350D3.5080200@codito.com>
no actually i am very very new to using
gdb so no i didnt know about scripting the
break points. how does that work?
jim
<html><DIV></DIV></html>
>From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
>To: james osburn <jjosburn@hotmail.com>
>CC: gdb@sources.redhat.com
>Subject: Re: tracing ( was Re: what are gdbstubs?)
>Date: Fri, 25 Mar 2005 05:14:19 +0530
>
>
>Hi,
>
>>sorry i should have been more specific.
>>a long long time ago (late 80s) borland
>>turbo c had a trace mode. it would start
>>a program and then just step line by
>>line through the code automatically.
>>you could control the speed and you
>>had the ability to see the registers and local
>>variables that where affected. again
>>the nice feature was that once this trace
>>feature was started it needed little user
>>interaction. i am looking
>>for some feature similar to that.
>
>Ok, you are looking for tracepoints in gdb . Its a similar feature but not
>totally the same .One needs to specify the tracepoints and the data to be
>collected. They are not supported with gdbserver AFAIK (of 6.3 vintage) .
>There have been some recent patches by Nathan Sidwell on tracepoints ,
>though I have not had the chance to look at what changes were being done.
>
>Another option is to script this up using gdb scripts / breakpoints and
>commands on hitting the breakpoints, but I guess you know that already.
>
>
>cheers
>Ramana
>
>
>
>>
>>thanks
>>jim
>>
>><html><DIV></DIV></html>
>>
>>
>>
>>>From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
>>>To: james osburn <jjosburn@hotmail.com>
>>>CC: gdb@sources.redhat.com
>>>Subject: Re: what are gdbstubs?
>>>Date: Fri, 25 Mar 2005 04:44:56 +0530
>>>
>>>james osburn wrote:
>>>
>>>>a m using uclibc on the 386 platform i am more interested
>>>>in tracing than setting break points.
>>>
>>>
>>>What do you exactly mean by tracing ? Function calls or get some other
>>>trace information ?
>>>
>>>
>>>>i want a way to remotely
>>>>what my program execute but i dont have a large budget
>>>>(hence the gnu tools)
>>>>any ideas on that?
>>>>jim
>>>>
>>>><html><DIV></DIV></html>
>>>>
>>>>
>>>>
>>>>>From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
>>>>>To: james osburn <jjosburn@hotmail.com>
>>>>>CC: gdb@sources.redhat.com
>>>>>Subject: Re: what are gdbstubs?
>>>>>Date: Fri, 25 Mar 2005 04:37:19 +0530
>>>>>
>>>>>Hi ,
>>>>>
>>>>>>I have been reading the gdb docs and as i interpret them
>>>>>>i need to link the gdb stub file with my excecuteable
>>>>>>to do remote debugging. is this correct?
>>>>>
>>>>>
>>>>>
>>>>>Yes you do.
>>>>>
>>>>>>do you have any experience with this?
>>>>>
>>>>>
>>>>>
>>>>>I have not used *-stub.c for any debugging in a while now. I must say
>>>>>however that if you were using linux / uClinux on your embedded system
>>>>>, you could choose to use gdbserver instead in which case the linking
>>>>>is not required.
>>>>>
>>>>>cheers
>>>>>Ramana
>>>>>
>>>>>
>>>>>--
>>>>>Ramana Radhakrishnan
>>>>>GNU Tools
>>>>>codito ergo sum (www.codito.com)
>>>>>
>>>>
>>>
>>>
>>>--
>>>Ramana Radhakrishnan
>>>GNU Tools
>>>codito ergo sum (www.codito.com)
>>>
>>
>
>
>--
>Ramana Radhakrishnan
>GNU Tools
>codito ergo sum (www.codito.com)
>
next prev parent reply other threads:[~2005-03-24 23:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 16:58 what are gdbstubs? james osburn
2005-03-24 17:08 ` Ramana Radhakrishnan
2005-03-24 22:55 ` james osburn
2005-03-24 23:08 ` Ramana Radhakrishnan
2005-03-24 23:12 ` james osburn
2005-03-24 23:15 ` Ramana Radhakrishnan
2005-03-24 23:25 ` tracing ( was Re: what are gdbstubs?) james osburn
2005-03-24 23:44 ` Ramana Radhakrishnan
2005-03-24 23:47 ` Daniel Jacobowitz
2005-03-24 23:48 ` james osburn [this message]
2005-03-24 23:59 ` Ramana Radhakrishnan
2005-03-25 0:09 ` Ramana Radhakrishnan
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=BAY13-F4029FB867B3C92AF7B57ACD8400@phx.gbl \
--to=jjosburn@hotmail.com \
--cc=gdb@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).