Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
To: <valgrind-developers@lists.sourceforge.net>
Cc: <gdb@sourceware.org>
Subject: Valgrind gdbserver patch : help needed for linux-arm/s390x/ppc32-64 and MacOS
Date: Sun, 20 Mar 2011 15:17:00 -0000	[thread overview]
Message-ID: <4273EBCDD5A84BBCB5A9A5556F454007@soleil> (raw)

I have attached a new version of the Valgrind gdbserver patch in 
https://bugs.kde.org/show_bug.cgi?id=214909

It should work on any x86/amd64 Linux (has been tested with gdb 7.2 on f12-x86, f14-amd64,
ubuntu10.10-x86, red-hat 5.2-amd64).

A previous version has been compiled and manually tested on Macos, so it should not be too difficult
to have it working on MacOS. I had only access during 3 hours to a Mac so for
MacOS, some more "ptrace related" work is needed in vgdb.c to have it fully functional
(i.e. allow gdb to "contact" a process with all threads blocked in a system call).

Linux-arm/s390x/ppc32/ppc64 : in theory, it should compile, and many fucntionalities
should work once compiled (e.g. external command handling, read/write memory,
breakpoints, etc).

To have it fully working (e.g. backtrace, info registers, ...), some (easy) work is needed
(e.g. in valgrind-low-arm.c, valgrind-low-s390x, etc ) to add
a 'switch' mapping the gdb registers to the valgrind registers
and to add a 'dummy call pusher' in vgdb.c.

Any feedback/comment (and help for platforms I do not have access to :) is welcome.

Philippe



                 reply	other threads:[~2011-03-20 15:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4273EBCDD5A84BBCB5A9A5556F454007@soleil \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb@sourceware.org \
    --cc=valgrind-developers@lists.sourceforge.net \
    /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