Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8252631
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T00:36:38+00:00 2026-06-08T00:36:38+00:00

Both executable and library are built with -g flags, but when I debug it

  • 0

Both executable and library are built with -g flags, but when I debug it with gdb it gives me error:
0x8b0cec83 in ?? () from last line of back trace. which I guess it is error from .so library I just built,
the shared library just filled some function pointers inside executable .How to debug both of them same time in gdb?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T00:36:40+00:00Added an answer on June 8, 2026 at 12:36 am

    There’s no additional steps required to debug the library. Chances are that the address you’re ending up at (0x8b0cec83) just isn’t part of either the application or the library, because you’re using an uninitialized (or corrupted) function pointer somewhere.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have built a shared library (i.e libabc.so ) and an executable (i.e myapp
Both of these frameworks are great, but I've noticed that Knockout likes to point
Both Network.Socket.ByteString and Network.Socket.ByteString.Lazy have a send function. Network.Socket.ByteString has a sendTo function, but
Both Ruby and Python have the ability of calling the debugger from code (
Both methods MyBehavior::CreateSerializer() are not called of some reason, but ReplaceBehavior() method is working.
My application consist of an executable project and a dll library. My executable project
I am trying to run an executable from a c++ program. I have looked
I've got a function imported from a DLL. I control the source of both
The following code compile well both with GCC (4.2-4.6) and with Clang (2.1), but
Is it a problem if I have an executable and a library use different

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.