On Fri, Apr 15, 2011 at 12:18, Tom Tromey wrote:
> A more "end-to-end" solution would be nice. What I mean by this is that
> right now the index generation is a separate step, and it involves
> running GDB, so for daily development it is basically not worth doing.
> It is only worthwhile in the R
> "Mark" == Mark Wielaard writes:
Mark> Do you think it makes sense to support printing this format, or will you
Mark> be arbitrarily changing it from time to time? Having it more prominently
Mark> documented would be nice.
We do change it from time to time.
We could document it elsewhere.
On Fri, 2011-04-15 at 08:54 -0600, Tom Tromey wrote:
> Ulrich> The best solution in that case is to have gdb provide
> Ulrich> the decoder.
>
> It does, in the form of binutils readelf --debug-dump=gdb_index.
Interesting, I didn't know that. Note that the version of binutils
readelf on fedora doe
Ulrich> The best solution in that case is to have gdb provide
Ulrich> the decoder.
It does, in the form of binutils readelf --debug-dump=gdb_index.
Tom
___
elfutils-devel mailing list
elfutils-devel@lists.fedorahosted.org
https://fedorahosted.org/mailma
On Fri, Apr 15, 2011 at 03:26, Mark Wielaard wrote:
> How does GNU standardization work BTW?
It works by all the relevant people agreeing about keeping things
stable and ideally writing it up in a form which a) can be looked up
by others (perhaps for re-implementation) and b) so they can be held
Hi,
I've used this Jim Meyering's script (thanks!) to find doubled words:
git ls-files .|xargs perl -0777 -n \
-e 'while (/\b(then?|in|an|it|on|if|at|but|f?or|and|to)\s+\1\b/gms)' \
-e '{$n=($` =~ tr/\n/\n/ + 1); ($v=$&)=~s/\n/\\n/g; print "$ARGV:$n:$v\n"}'
Here's a patch that fixes all thes
Hi Roland,
> I'm dubious about this. The .gdb_index format is not
> standardized even in the GNU sense.
How does GNU standardization work BTW?
Is there some GNU tools list?
> It's entirely gdb's private business. Unless and until
> it becomes a standard thing that an elfutils tool could generate
