From: Gary Benson <gbenson@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: proc_service.h as an installed header
Date: Wed, 06 Jul 2016 10:06:00 -0000 [thread overview]
Message-ID: <20160706100639.GB28876@blade.nx> (raw)
In-Reply-To: <05458564-05ab-349e-8702-8dbe8f50c3de@redhat.com>
Florian Weimer wrote:
> glibc has received a request to turn proc_service.h into an
> installed header:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=20311
>
> The request seems reasonable.
>
> The only question is who owns this API. glibc is just a consumer
> here, and the traditional provider is GDB, so I GDB would be the
> natural
I always thought of it as part of libthread_db's API.
i.e., thread_db.h is the debugger->libthread_db API,
and proc_service.h is the libthread_db->debugger API.
It seems like it'd be easier to provide it from glibc. If GDB
provided it glibc would have to carry its own copy anyway (I'm
presuming you don't want to introduce a build dependency on GDB)
> The API definitions seem to have drifted a bit, e.g.:
>
> --- glibc/git/nptl_db/proc_service.h
> +++ binutils-gdb/gdb/gdb_proc_service.h
> â¦
> -extern ps_err_e ps_pstop (const struct ps_prochandle *);
> -extern ps_err_e ps_pcontinue (const struct ps_prochandle *);
> +extern ps_err_e ps_pstop (struct ps_prochandle *);
> +extern ps_err_e ps_pcontinue (struct ps_prochandle *);
>
> Perhaps we should clean this up before making this a more public API?
Yeah, I think the API was defined to match what the Solaris guys were
doing with it, and that doesn't match well what glibc does. There's
a fair few places where glibc's libthread_db casts away const.
Cheers,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2016-07-06 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 18:29 Florian Weimer
2016-07-06 10:06 ` Gary Benson [this message]
2016-07-19 18:35 ` Pedro Alves
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=20160706100639.GB28876@blade.nx \
--to=gbenson@redhat.com \
--cc=fweimer@redhat.com \
--cc=gdb@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