Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: shravan <shravanrn@gmail.com>
To: gdb@sourceware.org
Subject: How does GDB load source line information during dlopen calls
Date: Fri, 05 Jan 2018 06:48:00 -0000	[thread overview]
Message-ID: <CAEmVGBqADgFi3pAxAbH+5AE35VfZkvVPQDMSM+fHAZXVEhr1Dw@mail.gmail.com> (raw)

Hi all,
First time poster to this list - so please bear with me :)
I am currently working on a project that has a custom dynamic loader for
shared libraries in the ELF format - it does NOT use dlopen. When debugging
this dynamically loaded library, I am hoping to be able to single step
through the C source code of functions in the library in tui mode.

If I had use dlopen this would work fine, but this does not work using the
custom dynamic loader. I am able to get the libraries symbols loaded with
"add-symbol-file". However the src line information is still not working.
For example "list someFunctionInLibrary" prints nothing and "layout src"
shows a blank screen

I am hoping for any information or suggestions. Is there some way to hint
to gdb to load the source line information from a particular file at a
particular address?

(Also please let me know if there is a better venue for the question).

Thanks!
Shravan


             reply	other threads:[~2018-01-05  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05  6:48 shravan [this message]
2018-01-08 16:04 ` Simon Marchi
     [not found]   ` <CAEmVGBpNPeVqMed4AF5gLMASswi+7-PoCwKKUDP4OvVhpVdppQ@mail.gmail.com>
     [not found]     ` <CAEmVGBq5UQHr0HOoqWOZ6j8M=yh1K4J+ioaBZYUSjWYSpVN+aA@mail.gmail.com>
2018-01-09  3:38       ` shravan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEmVGBqADgFi3pAxAbH+5AE35VfZkvVPQDMSM+fHAZXVEhr1Dw@mail.gmail.com \
    --to=shravanrn@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox