Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] catch syscall -- try 4 -- Architecture-independent 	part
Date: Thu, 09 Apr 2009 19:29:00 -0000	[thread overview]
Message-ID: <1239305373.6452.13.camel@miki> (raw)
In-Reply-To: <20090331154452.GA13260@caradoc.them.org>

Hi Daniel,

On Tue, 2009-03-31 at 11:44 -0400, Daniel Jacobowitz wrote:
> On Sun, Mar 29, 2009 at 03:50:26PM -0300, Sérgio Durigan Júnior wrote:
> > ~"Catchpoint 1 (call to syscall 'chroot'), 0xffffe424 in
> > __kernel_vsyscall ()\n"
> > ~"0xffffe424 <__kernel_vsyscall+16>:\tpop    %ebp\n"
> > *stopped,frame={addr="0xffffe424",func="__kernel_vsyscall",args=[]},thread-id="1",stopped-threads="all"
> 
> > So, what do you think of it? Analyzing it, I think it's not so useful
> > except for the (obvious) part ~"Catchpoint 1 ...".
> 
> Right.  There ought to be a new reason="..." entry; search for
> EXEC_ASYNC_BREAKPOINT_HIT.  There should probably be some semantic
> fields, too, like "old" for watchpoints.

I'm sorry about taking so long to reply your messages, but I'm really
busy with other things here. By the way, that's one of the reasons why
I'm asking this...

Well, I perfectly understand when you (or anyone else here in GDB) ask
me to implement something else in the catch syscall patch, after all
it's important to have a good code in GDB's codebase. But honestly, this
time I think you're exaggerating a little. I know that it would be cool
to have the MI support in the catch syscall feature, and I myself plan
to implement this support in a future not so distant; however, and
specially because I'm very busy these days, I won't be able to dedicate
enough time in order to get it ready for GDB 7.0, and IMHO the catch
syscall would be a *nice* feature to have in this release.

So this is my opinion about this: I have the complete catch syscall
patch here (the only thing that's missing is the MI support), so what do
you think if we just push this patch upstream as-is (which is: in a
pretty good shape, as far as I understood the others developers' --
including yours -- comments), and postpone this MI support? I think I
should be able to sit down and implement this support until the end of
this semester, is it good for you?

Well, thanks for your time, for your valuable reviews about my code, and
for your patience. Please consider my proposal and let me know what you
think about it.

Regards,

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil


  reply	other threads:[~2009-04-09 19:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  0:31 Sérgio Durigan Júnior
2009-01-26  0:51 ` Pedro Alves
2009-01-26  4:56   ` Sérgio Durigan Júnior
2009-01-26 17:04     ` Sérgio Durigan Júnior
2009-02-01 19:33       ` Daniel Jacobowitz
2009-02-25 21:44         ` Sérgio Durigan Júnior
2009-02-28  0:44           ` Daniel Jacobowitz
2009-03-08 18:16             ` Sérgio Durigan Júnior
2009-03-09 13:19               ` Daniel Jacobowitz
2009-03-09 14:09                 ` Sérgio Durigan Júnior
2009-03-09 18:39                   ` Pedro Alves
2009-03-09 18:56                     ` Daniel Jacobowitz
2009-03-09 18:31                 ` Pedro Alves
2009-03-29 21:16             ` Sérgio Durigan Júnior
2009-03-31 16:39               ` Daniel Jacobowitz
2009-04-09 19:29                 ` Sérgio Durigan Júnior [this message]
2009-04-09 19:36                   ` Daniel Jacobowitz
2009-04-09 20:21                     ` Sérgio Durigan Júnior
2009-04-15 23:12                 ` Sérgio Durigan Júnior

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=1239305373.6452.13.camel@miki \
    --to=sergiodj@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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