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

  • SEARCH
  • Home
  • 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 6164213
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T21:57:20+00:00 2026-05-23T21:57:20+00:00

Ubuntu 10.10, GDB 7.2. I attach to an application, watch stacks in every thread,

  • 0

Ubuntu 10.10, GDB 7.2.
I attach to an application, watch stacks in every thread, everything looks good. Do generate-core-file and try to open that coredump in gdb. No routines is shown in backtraces.

I send SIGSEGV to the application and open this new coredump in gdb. Stacks are ok and verbose.

Please tell me if you experienced a similar incorrect behaviour of generate-core-file.

  • 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-05-23T21:57:20+00:00Added an answer on May 23, 2026 at 9:57 pm

    This is a known bug in GDB. The link has also a patch for fixing the problem.

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

Sidebar

Related Questions

I am currently running gdb version 6.7.1 on Ubuntu Linux, and working in a
Ubuntu Server 9.10, Here is my file, test.py import commands blkid = commands.getoutput('blkid') print
Seen with gdb on openSUSE, CentOS, Fedora, and Ubuntu: This gdb was configured as
Just curious. Using gcc/gdb under Ubuntu 9.10. Reading a C book that also often
I am running a Python GUI application. I want to invoke and control GDB
Ubuntu Server 11.10 How to rename file .test to test ? rename .test test
Ubuntu: Jaunty Mercurial: 1.3.1 Access: ssh (users john and bob) File permission: -rw-rw---- 1
GDB, at least as it's configured by default on my Ubuntu 9.04 box, doesn't
I'm using pthread_cond_timedwait on a thread loop to execute at every X ms (unless
When I run GDB with BACKTRACE command locally (Ubuntu 10.10) I am getting this

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.