Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Enhance GDB to break inside DSO init code
Date: Fri, 27 Aug 2004 13:39:00 -0000	[thread overview]
Message-ID: <20040827133945.GC1829@gnat.com> (raw)
In-Reply-To: <20040824164507.11b04f11@saguaro>

Hello Kevin,

> Do you have access to a Solaris box?  If so, could you test for
> regressions there as well?

That's a good idea. So I tested the patch on sparc-solaris2.8 as well,
without any regression.

> If all goes well, I have no objection to this patch going in.  (Consider
> it approved unless someone else says otherwise.)

I didn't see any objection, so I checked the patch in. Thank you for
the review!

> > 2004-07-23  Joel Brobecker  <brobecker@gnat.com>
> > 
> >         * procfs.c (dbx_link_bpt_addr): New static global variable.
> >         (dbx_link_shadow_contents): New static global variable.
> >         (procfs_wait, case <PR_SYSEXIT>): Handle syssgi events.
> >         (procfs_wait, case <FLTBPT>): Remove the __dbx_link brekapoint
> >         if we just hit it.
> >         (procfs_init_inferior): Enable syssgi() syscall trace if appropriate.
> >         Reset dbx_link_bpt_addr as the address of __dbx_link() may change
> >         from run to run.
> >         (procfs_create_inferior): Remove syssgi syscall-exit notifications
> >         after the inferior has been forked.
> >         (remove_dbx_link_breakpoint): New function.
> >         (dbx_link_addr): New function.
> >         (insert_dbx_link_bpt_in_file): New function.
> >         (insert_dbx_link_bpt_in_region): New function.
> >         (insert_dbx_link_breakpoint): New function.
> >         (proc_trace_syscalls_1): New function, extracted from
> >         proc_trace_syscalls.
> >         (proc_trace_syscalls): Replace extract code by call to
> >         proc_trace_syscalls_1.
> >         * solib-irix.c (disable_break): Remove stop_pc assertion, as it
> >         is no longer valid.
> > 
> > Tested on mips-irix, no regression. OK to commit?
-- 
Joel


      reply	other threads:[~2004-08-27 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 20:24 Joel Brobecker
2004-07-24  7:56 ` Eli Zaretskii
2004-07-24 15:01   ` Joel Brobecker
2004-07-24 17:16     ` Eli Zaretskii
2004-08-06 18:31 ` Joel Brobecker
2004-08-19  7:55 ` Joel Brobecker
2004-08-24 23:45 ` Kevin Buettner
2004-08-27 13:39   ` Joel Brobecker [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=20040827133945.GC1829@gnat.com \
    --to=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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