From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] procfs.c: Remove unused functions and make many functions static
Date: Thu, 17 May 2012 17:35:00 -0000 [thread overview]
Message-ID: <20120517173453.GF10253@adacore.com> (raw)
In-Reply-To: <1336000479-30511-1-git-send-email-brobecker@adacore.com>
> gdb/ChangeLog:
>
> * procfs.c (procfs_find_new_threads, procfs_pid_to_str,
> proc_warn, proc_error, proc_get_status, proc_flags,
> proc_why, proc_what, proc_nsysarg, proc_sysargs,
> proc_set_run_on_last_close, proc_unset_run_on_last_close,
> proc_unset_inherit_on_fork, proc_set_async, proc_unset_async,
> proc_stop_process, proc_wait_for_stop, proc_run_process,
> proc_set_traced_signals, proc_set_traced_faults,
> proc_set_traced_sysentry, proc_set_traced_sysexit,
> proc_set_held_signals, proc_get_held_signals,
> proc_get_traced_signals, proc_get_traced_faults,
> proc_get_traced_sysentry, proc_get_traced_sysexit,
> proc_clear_current_fault, proc_set_current_signal,
> proc_clear_current_signal, proc_get_gregs, proc_get_fpregs,
> proc_set_gregs, proc_set_fpregs, proc_kill, proc_parent_pid,
> proc_get_nthreads, proc_get_nthreads, proc_get_nthreads,
> proc_get_current_thread, proc_get_current_thread,
> proc_get_current_thread, proc_update_threads,
> proc_update_threads, proc_update_threads, proc_update_threads,
> proc_iterate_over_threads, procfs_find_new_threads,
> procfs_pid_to_str): Make static. Remove advance declaration.
> (proc_cursig): Make static. Conditionalized defintion on
> PROCFS_DONT_PIOCSSIG_CURSIG being defined.
> (proc_syscall, proc_set_kill_on_last_close,
> proc_unset_kill_on_last_close, proc_set_inherit_on_fork,
> proc_get_pending_signals, proc_get_signal_actions,
> proc_trace_signal, proc_ignore_signal): Delete.
[...]
Maciej asked:
> Hmm, here's a dumb question as a followup, following a situation I've
> just experienced -- can this stuff be needed by anything external on
> Solaris, similarly to some functions pulled from GDB by libthread_db.so.1
> from glibc?
Sorry for the delay in answering this. I just couldn't find the time
to look at it.
I think we will be fine. Usually, implicit callbacks have a specific
name that ties them to the external shared library that needs those
callbacks, and the fact that the name of the functions being deleted
start with the same prefix as the others is a little indicative that
the odds of them being an implicit callback are small. Regardless,
I did a little bit of research, and found that, AFAICT, this file
is only used on sparc/x86/amd64-solaris, mips-irix¬ and alpha-tru64.
I looked at the extra source files needed by these platforms, and
none of them indicated that we would open a shared library that might
call one of these functions. Just for kicks, I tested the patch on
sparc-solaris using AdaCore's testsuite.
So I have now checked the patch in.
--
Joel
next prev parent reply other threads:[~2012-05-17 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 23:15 Joel Brobecker
2012-05-04 9:10 ` Maciej W. Rozycki
2012-05-04 12:35 ` Joel Brobecker
2012-05-04 22:49 ` Maciej W. Rozycki
2012-05-07 8:24 ` Maciej W. Rozycki
2012-05-17 17:35 ` Joel Brobecker [this message]
2012-05-17 19:26 ` Maciej W. Rozycki
2012-05-17 20:43 ` Joel Brobecker
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=20120517173453.GF10253@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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