Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Pouget <kevin.pouget@gmail.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Global breakpoints, introduction
Date: Tue, 14 Jun 2011 09:39:00 -0000	[thread overview]
Message-ID: <BANLkTi=Oba8x_oc1ri+M6rZBp2aBxRQZTQ@mail.gmail.com> (raw)
In-Reply-To: <4DF642D0.9050200@earthlink.net>

Hello,

the idea is very interesting, I'll certainly have to use it soon!

>  fprintf_unfiltered (gdb_stdlog, "target_to_define_global_breakpoint (0x%x, %s, %s, %d) = %d\n",
>		      (int) abfd, paddress (target_gdbarch, addr),
>		      (uname ? uname : "<NULL>"), flags, rslt);

target.c:4200: error: cast from pointer to integer of different size
[-Werror=pointer-to-int-cast]


and in the README, you mention the file "/proc/drivers/breakpoints"
whereas it's certainly /proc/driver/breakpoint


cordially,

Kevin

On Mon, Jun 13, 2011 at 7:03 PM, Stan Shebs <stanshebs@earthlink.net> wrote:
>
> On 6/13/11 9:39 AM, Frank Ch. Eigler wrote:
>>
>> Hi, Stan -
>>
>> stanshebs wrote:
>>
>>> This pair of patches plus Linux kernel module adds global breakpoints
>>> to GDB.  [...]
>>
>> Interesting approach.  Have you been planning to post it to LKML for
>> review/consideration?
>>
>
> Yes, I've just been waiting for all the debugger-haters there to retire and/or die first. :-)
>
>> You may want to rebase your code to the LKML uprobes implementation
>> already under review, so you don't have to duplicate the rather
>> intricate logic required to safely manage breakpoints in userspace by
>> the kernel.
>
> That's a good idea!  I haven't updated myself on uprobes state in the past several months, but you're right, it would be good to have a single version of that.
>
> Stan
>


      reply	other threads:[~2011-06-14  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 15:58 Stan Shebs
2011-06-13 16:39 ` Frank Ch. Eigler
2011-06-13 17:03   ` Stan Shebs
2011-06-14  9:39     ` Kevin Pouget [this message]

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='BANLkTi=Oba8x_oc1ri+M6rZBp2aBxRQZTQ@mail.gmail.com' \
    --to=kevin.pouget@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.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