unable to find source line info for address
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 112
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Sorry for leaving this message here because I do not know how to solve this problem.
I have tried using bfd and dwarf/elf to convert the binary to the source line number but all failed.
mpiP Configuration Summary
C compiler : mpicc
C++ compiler : mpicxx
Fortran compiler : mpif90
Timer : MPI_Wtime
Stack Unwinding : libunwind
Address to Source Lookup : bfd
MPI-I/O support : yes
MPI-RMA support : yes
MPI-NBC support : yes
-------------------------------------------------------------------------------------------------------------------------------------------------------------
mpiP Configuration Summary
C compiler : mpicc
C++ compiler : mpicxx
Fortran compiler : mpif90
Timer : MPI_Wtime
Stack Unwinding : libunwind
Address to Source Lookup : libelf/libdwarf
MPI-I/O support : yes
MPI-RMA support : yes
MPI-NBC support : yes
---------------------------------------------------------------------------------------------------------------------------------------------------------------
The source line of the output always look like this:
28 @--- Callsites: 4 ---------------------------------------------------------
29 ---------------------------------------------------------------------------
30 ID Lev File/Address Line Parent_Funct MPI_Call
31 1 0 0x7fe7d3ae7b2a [unknown] Recv
32 2 0 0x7f260692259a [unknown] Send
33 3 0 0x7f1637a7859a [unknown] Send
34 4 0 0x7f044e9dc59a [unknown] Send
Can someone point me to the right direction? Much appreciated!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository files, tests, or entry points. Start by reproducing the callsite output with the shown bfd and libelf/libdwarf configurations, then trace the address-to-source lookup path. Done means valid source file and line information is reported instead of [unknown] for the affected addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100