Bug 167694 - Uninitialised free when running "info line main"
Uninitialised free when running "info line main"
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gdb (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnston
Jay Turner
Depends On:
Blocks: 168429
  Show dependency treegraph
Reported: 2005-09-07 05:55 EDT by Bastien Nocera
Modified: 2015-01-07 19:10 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2006-0106
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-07 13:19:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gdb-info-list-main-uninit-free.patch (544 bytes, patch)
2005-09-07 05:55 EDT, Bastien Nocera
no flags Details | Diff

  None (edit)
Description Bastien Nocera 2005-09-07 05:55:16 EDT
+++ This bug was initially created as a clone of Bug #167693 +++

1. create a small hello world C program
2. compile it with debugging
3. run the program under gdb
4. type "info line main" in gdb
5. segfault

Reproduceable with the RHEL3 U5 gdb, and the RHEL4 U2 candidate.

valgrind says there's an invalid free:
==21896== Invalid free() / delete / delete[]
==21896==    at 0x3414A75D: free (vg_replace_malloc.c:153)
==21896==    by 0x80F3229: find_line_pc_range (symtab.c:2432)
==21896==    by 0x80DE1D9: ??? (source.c:1351)
==21896==    by 0x80845C5: execute_command (top.c:733)
==21896==  Address 0x9C5FDEE8 is on thread 1's stack
Line 5 of "tmp.c" starts at address 0x8048368 <main>
  and ends at 0x8048384 <main+28>.

In gdb/symtab.c, find_line_pc_range(), pc_list is only defined if startaddr is
0, but freed unconditionally. Patch attached.
Comment 1 Bastien Nocera 2005-09-07 05:55:17 EDT
Created attachment 118547 [details]
Comment 2 Jeff Johnston 2005-09-22 17:51:43 EDT
As of gdb-, the patch has been incorporated.
Comment 19 Red Hat Bugzilla 2006-03-07 13:19:04 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.