Re: readelf utility concatenates underscores to fortran variables with underscores
From: Scott Lurndal (scott_at_slp53.sl.home)
Date: 02/08/04
- Next message: David: "P2P stopped all network traffic"
- Previous message: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- In reply to: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- Next in thread: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- Reply: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 08 Feb 2004 16:40:12 GMT
clusardi2k@aol.com (Christopher M. Lusardi) writes:
>scott@slp53.sl.home (Scott Lurndal) wrote in message news:<mXRUb.20986$6W3.15983@newssvr27.news.prodigy.com>...
>> clusardi2k@aol.com (Christopher M. Lusardi) writes:
>> >Hello,
>> >
>> >C File test.f
>> >
>> > program main
>> > integer test1
>> > integer test_10
>> > common /test/ test1,test_10
>> > end
>> >
>> >C compile :
>> >C f77 -g test.f
>> >
>> > When I do readelf -w --debug-dump=info a.out, and look at the ouput. All my
>> >Fortran common variables containing at least 1 underscore get converted into
>> >having 2 extra underscores in the output. Is there any way that I can prevent
>> >readelf from adding the additional underscores?
>>
>> Readelf is _not_ adding the extra underscores. The compiler is. Why does it
>> matter to you?
>>
>> scott
>
>I'm creating a debugger program, and I was hoping to make my program more
>portable. Anyway, I can force my program to look for a trailing "__" and a "_"
>before that and then strip off the "__". I'll do this unless you can suggest
>a better way to do this.
>
>Christopher Lusardi
For reasons such as the above, debuggers are generally specific to the
compiler suite which generates the object code being debugged. C++
name demangling is another area in which portability will no be
assured. There may also be platform specific areas such as signal
trampolining and c-runtime startup code (crt.0) which are not generally
portable that the debugger will need to be aware of.
You should be able to abstract out the non-portable features into a
platform dependent layer of your debugger.
scott
- Next message: David: "P2P stopped all network traffic"
- Previous message: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- In reply to: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- Next in thread: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- Reply: Christopher M. Lusardi: "Re: readelf utility concatenates underscores to fortran variables with underscores"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|