Bug 52494 - debugging graphical program is not possible
Summary: debugging graphical program is not possible
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: gdb   
(Show other bugs)
Version: roswell
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-24 10:28 UTC by Pawel Salek
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-24 15:33:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Pawel Salek 2001-08-24 10:28:07 UTC
Description of problem:
It is not possible to set a breakpoint in many GUI programs (and possibly
in other classes of programs, too). One gets:
Error in re-setting breakpoint 1:
Cannot access memory at address 0x123


Version-Release number of selected component (if applicable):
gdb-5.0rh-15

How reproducible:
Always

Steps to Reproduce:
1.gdb /usr/bin/gless
2.break main (at gdb prompt)
3.run

	

Actual Results:  (gdb) b main
Breakpoint 1 at 0x804a3a6
(gdb) run
Starting program: /usr/bin/gless 
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...Error in re-setting breakpoint 1:
Cannot access memory at address 0x123
Error in re-setting breakpoint 1:
Cannot access memory at address 0x123
Error in re-setting breakpoint 1:
Cannot access memory at address 0x123
Error in re-setting breakpoint 1:


Expected Results:  The breakpoint is set and program stops in main.

Comment 1 Trond Eivind Glomsrxd 2001-08-24 15:18:22 UTC
Does it work if you build the program with debugging information?

Comment 2 Pawel Salek 2001-08-24 15:33:52 UTC
Well, adding -g option fixed debuggin the first program I had at hand. That's
promising.

Anyway, recompiling a program is not always an option, IMO.

Comment 3 Trond Eivind Glomsrxd 2001-08-24 15:38:10 UTC
Without the binary compiled for debugging, you can't debug it.

Comment 4 Pawel Salek 2001-08-24 15:56:29 UTC
Assuming the statement above to be true, gdb should inform the user instead of
pretenting to be confused.


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