Re: R: Improvements in binutils by implementing libaddr2line.a

[Nick Clifton <nickc at redhat dot com>]

Hi Massimo,

  [Please keep the CC to the binutils mailing list.  Discussions like this 
should be held on the public list].

> I don't know how to obtain an FSF copyright assignment from FSF.

I have attached a form to this reply which you can use to start the application 
process, should you choose to do so.

> But anyway I did only a few modifications on the addr2line.c file and the
> part I have added/modified has been copied from gnaddr2line.c files found in
> http://www.filewatcher.com/p/binutils-2.15.90-20040222-1-src.tar.gz.14182109
> /binutils-2.15.90-20040222-1/binutils/gnaddr2line.c.html

Hmm, unfortunately there does not appear to be any description of who made 
these changes to addr2line.c or why.

> But I agree with you that it is more flexible to insert it in bfd. In this
> manner there isn't one more library and it is strictly correlated with bfd
> library. I think that the procedure will be useful also for all the program
> using execinfo.h.

True, but honestly I do not see what benefit this proposed library function 
would have over the already existing bfd_find_nearest_line() function.  The 
only thing that the translate_address() and convert_address() functions add is 
the ability to process more than one address at a time, and that is easily 
handled by a simple loop in the caller of bfd_find_nearest_line.

Really is there any benefit to having the proposed convert_address() function 
in the bfd library ?  I am attaching a version of the prova_bt.c program that 
you supplied but edited to use bfd_find_nearest_line instead of 
convert_address.  The results are pretty much the same in my opinion.

Cheers
  Nick

---------------------------------------------------------------------------

request-assign.future:

Please email the following information to fsf-records@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full name as the subject line of the message.


[What is the name of the program or package you're contributing to?]


[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your snail address here.]





[Which files have you changed so far, and which new files have you written
so far?]





---------------------------------------------------------------------------

Attachment: prova_bt.c
Description: application/unknown-content-type-c_auto_file