public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* RE: regarding tracepoint support on a stub
@ 2003-11-03 19:01 Newman, Mark (N-Superior Technical Resource Inc)
  2003-11-03 19:21 ` Daniel Jacobowitz
  0 siblings, 1 reply; 3+ messages in thread
From: Newman, Mark (N-Superior Technical Resource Inc) @ 2003-11-03 19:01 UTC (permalink / raw)
  To: ankit thukral, gdb

Would it be desireable to drop ptrace all together and start looking at
using /proc in gdbserver?

The man pages (both Sun's and GNU's) refer to ptrace as "unique and
arcane".

             Mark Newman


> -----Original Message-----
> From: gdb-owner@sources.redhat.com
> [mailto:gdb-owner@sources.redhat.com]On Behalf Of ankit thukral
> Sent: Monday, November 03, 2003 1:24 AM
> To: gdb@sources.redhat.com
> Subject: regarding tracepoint support on a stub
> 
> 
> hi all,
>       i was going through the GDB support for
> tracepoints and the packets it sends to the stub.i
> thought of collecting the registers on the gdbserver
> side using a single ptrace to collect all the
> registers and then store the ones requested instead of
> a ptrace for each register. the problem i now face is
> : there are 3 different ptrace requests for collecting
> registers,viz,PTRACE_GETREGS, PTRACE_GETFPREGS and
> PTRACE_GETFPAREGS.how do i determine (on the stub
> side) which of these to call as i don't have anything
> on the GDBSERVER side (or so i guess) which would
> categorize a register to an integer or a float
> register.
>       also,please suggest if there is a better way in
> which i can accomplish the above(i.e.,implementation
> of collecting registers in a better way). 
> 
> thanks in advance,
> ankit.
> 
> __________________________________
> Do you Yahoo!?
> Exclusive Video Premiere - Britney Spears
> http://launch.yahoo.com/promos/britneyspears/
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: regarding tracepoint support on a stub
  2003-11-03 19:01 regarding tracepoint support on a stub Newman, Mark (N-Superior Technical Resource Inc)
@ 2003-11-03 19:21 ` Daniel Jacobowitz
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2003-11-03 19:21 UTC (permalink / raw)
  To: Newman, Mark (N-Superior Technical Resource Inc); +Cc: ankit thukral, gdb

On Mon, Nov 03, 2003 at 02:01:23PM -0500, Newman, Mark (N-Superior Technical Resource Inc) wrote:
> Would it be desireable to drop ptrace all together and start looking at
> using /proc in gdbserver?

/proc in Linux can not serve as a replacement for ptrace.  The
functionality is not there.

> 
> The man pages (both Sun's and GNU's) refer to ptrace as "unique and
> arcane".
> 
>              Mark Newman
> 
> 
> > -----Original Message-----
> > From: gdb-owner@sources.redhat.com
> > [mailto:gdb-owner@sources.redhat.com]On Behalf Of ankit thukral
> > Sent: Monday, November 03, 2003 1:24 AM
> > To: gdb@sources.redhat.com
> > Subject: regarding tracepoint support on a stub
> > 
> > 
> > hi all,
> >       i was going through the GDB support for
> > tracepoints and the packets it sends to the stub.i
> > thought of collecting the registers on the gdbserver
> > side using a single ptrace to collect all the
> > registers and then store the ones requested instead of
> > a ptrace for each register. the problem i now face is
> > : there are 3 different ptrace requests for collecting
> > registers,viz,PTRACE_GETREGS, PTRACE_GETFPREGS and
> > PTRACE_GETFPAREGS.how do i determine (on the stub
> > side) which of these to call as i don't have anything
> > on the GDBSERVER side (or so i guess) which would
> > categorize a register to an integer or a float
> > register.
> >       also,please suggest if there is a better way in
> > which i can accomplish the above(i.e.,implementation
> > of collecting registers in a better way). 
> > 
> > thanks in advance,
> > ankit.
> > 
> > __________________________________
> > Do you Yahoo!?
> > Exclusive Video Premiere - Britney Spears
> > http://launch.yahoo.com/promos/britneyspears/
> > 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

^ permalink raw reply	[flat|nested] 3+ messages in thread

* regarding tracepoint support on a stub
  2003-10-31  8:03 GDB Remote Debugging Problem Kiran Chandrashekaran, Nair (IE10)
@ 2003-11-03  6:24 ` ankit thukral
  0 siblings, 0 replies; 3+ messages in thread
From: ankit thukral @ 2003-11-03  6:24 UTC (permalink / raw)
  To: gdb

hi all,
      i was going through the GDB support for
tracepoints and the packets it sends to the stub.i
thought of collecting the registers on the gdbserver
side using a single ptrace to collect all the
registers and then store the ones requested instead of
a ptrace for each register. the problem i now face is
: there are 3 different ptrace requests for collecting
registers,viz,PTRACE_GETREGS, PTRACE_GETFPREGS and
PTRACE_GETFPAREGS.how do i determine (on the stub
side) which of these to call as i don't have anything
on the GDBSERVER side (or so i guess) which would
categorize a register to an integer or a float
register.
      also,please suggest if there is a better way in
which i can accomplish the above(i.e.,implementation
of collecting registers in a better way). 

thanks in advance,
ankit.

__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-11-03 19:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-03 19:01 regarding tracepoint support on a stub Newman, Mark (N-Superior Technical Resource Inc)
2003-11-03 19:21 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-10-31  8:03 GDB Remote Debugging Problem Kiran Chandrashekaran, Nair (IE10)
2003-11-03  6:24 ` regarding tracepoint support on a stub ankit thukral

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).