Bug 111183 - gdb fails horribly if program linked with -pie
gdb fails horribly if program linked with -pie
Status: CLOSED DUPLICATE of bug 99228
Product: Fedora
Classification: Fedora
Component: gdb (Show other bugs)
1
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Elena Zannoni
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-11-28 21:51 EST by Valdis Kletnieks
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:00:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
typescript demonstrating the problem (1.61 KB, text/plain)
2003-11-28 21:53 EST, Valdis Kletnieks
no flags Details

  None (edit)
Description Valdis Kletnieks 2003-11-28 21:51:45 EST
Description of problem:
gdb is unable to set breakpoints or provide tracebacks if program is
linked with -pie

Version-Release number of selected component (if applicable):
GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh)

How reproducible:
See attached typescript

Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Valdis Kletnieks 2003-11-28 21:53:48 EST
Created attachment 96247 [details]
typescript demonstrating the problem
Comment 2 Nathan Bryant 2004-01-13 12:20:14 EST
looks like your compilation options may be wrong. shouldn't you have
used -pie -fpie?
Comment 3 Nathan Bryant 2004-01-13 12:36:23 EST
sorry false alarm i was able to reproduce this with -pie -fpie. this
may be what is causing me problems debugging mozilla
Comment 4 Nathan Bryant 2004-01-13 12:44:51 EST
This is a duplicate of bug 99228
Comment 5 Elena Zannoni 2004-01-13 13:55:30 EST
I am closing this. Look at 99228 from now on.

*** This bug has been marked as a duplicate of 99228 ***
Comment 6 Red Hat Bugzilla 2006-02-21 14:00:13 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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