gcore fails to create a core dump if the terminal window is filled with output

Solution Verified - Updated -

Issue

  • gcore fails to create a core dump for a running program if the terminal window is filled with many lines of output from gdb

Environment

  • Red Hat Enterprise Linux 5 Update 4

  • kernel: 2.6.18-164.el5

  • gdb-6.8-37.el5
  • A program that causes gdb to print many lines -- more than a screenful -- of output.  A program that's linked to a large number of shared libraries will do this; for each shared library, if the debuginfo packages are not installed, gdb will print the message "no debugging symbols found".

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.