This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patchv3 0/8] Validate binary before use
- From: Pedro Alves <palves at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Aleksandar Ristovski <ARistovski at qnx dot com>
- Date: Mon, 03 Mar 2014 13:27:14 +0000
- Subject: Re: [patchv3 0/8] Validate binary before use
- Authentication-results: sourceware.org; auth=none
- References: <20140227213229 dot GA21121 at host2 dot jankratochvil dot net> <5310933E dot 8000601 at redhat dot com> <20140302183659 dot GA11910 at host2 dot jankratochvil dot net>
On 03/02/2014 06:36 PM, Jan Kratochvil wrote:
as it partially overlaps my non-upstreamed "locate
> files by their build-id from a core file":
> http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-6.6-buildid-locate.patch
>
>
>> BTW, do you plan on contributing support for validation with cores too?
>
> No.
OK. I think it'd be useful, so that GDB can warn/reject in the
common scenario of the user not pointing at a sysroot with the
correct DSOs.
If related I find right to extend gdbserver to support cores, it would be
> useful for ABRT to prevent needless uploads of many MBs of compressed core
> files. I have added "core file loading " to:
> https://sourceware.org/gdb/wiki/LocalRemoteFeatureParity?action=diff&rev2=56&rev1=55
Thanks. I think that feature may be a little beyond borderline
for that project page though, as core loading is not really part
of the native target. IMO it'd good if this had its own project
page, where it'd give answer to questions like the below.
#0 - If implemented by gdbserver, it seems like it'd involve further user
action to trigger the feature? How does one tell GDB/gdbserver to load the
ore on the remote side rather than locally?
#1 - couldn't this be addressed by just using fuse/ssh/somesuch to
access the core? (that is, transparently from GDB).
#2 - if not, could we perhaps tweak the target stratum bits a little to
allow sitting core_ops on top of extended-remote, and have it read the
necessary bits off the remote core with target_fileio_xxx. So we'd
still have host-side core_ops / bfd. You'd load the core with e.g.,
"core remote:/.../core.pid").
>>> --- a/gdb/testsuite/gdb.base/solib-mismatch.exp
>>> +++ b/gdb/testsuite/gdb.base/solib-mismatch.exp
>>> @@ -1,4 +1,4 @@
>>> -# Copyright 2013 Free Software Foundation, Inc.
>>> +# Copyright 2014 Free Software Foundation, Inc.
>>
>> These need to be 2013-2014.
>
> Why? It counts since the first post to gdb-patches?
https://sourceware.org/ml/gdb-patches/2014-02/msg00859.html
--
Pedro Alves