Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Getting callstack information

Open
  • Is something wrong?
#36 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
distributed-systems, performance

Research direction

Review mpiP's documented build and profiling steps, starting with the existing -g build and a profile containing MPI calls. Reproduce the report and identify the additional symbol or callstack setup required; done means the profile shows the calling function and source-file names.

Written by the indexing model from the issue text.

Description

I'd like to know which functions in the code are making the MPI calls shown in the profile. I compiled the code with -g, and still the function or source file names are not shown. What additional steps do I need to take to get that information?
Thanks.

Dominant language
C
Stars
112
Forks
35
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from llnl/mpiP

All issues in llnl/mpiP

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.