Bug 148769 - gdb breakpoints does not work where path to executable contains parentheses ()
Summary: gdb breakpoints does not work where path to executable contains parentheses ()
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 3.4.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-12 14:03 UTC by Alexander GALANIN
Modified: 2007-08-20 19:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander GALANIN 2007-08-12 14:03:29 UTC 
Version:           3.4.0 (using KDE 3.5.7, Debian Package 4:3.5.7.dfsg.1-1 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.21-2-amd64

gdb breakpoints does not work where path to executable contains parentheses ()
Comment 1 Andreas Pakulat 2007-08-19 18:51:41 UTC 
Does commandline gdb work with that executable?
Comment 2 Alexander GALANIN 2007-08-20 07:48:12 UTC 
Sorry, I don't know how to run gdb from command line. Can you give an example?
But gdb breakpoints works well if path doesn't contain parenthesis.
Comment 3 Andreas Pakulat 2007-08-20 11:05:09 UTC 
Just run gdb yourexecutable and then try to set a breakpoint in some file, for example main.cpp:

break /absolute/path/to/project/main.cpp:55

where you substitute the real path and a proper line instead of the 55. Then execute:

run

so your application starts and should stop at the breakpoint.

If it doesn't stop at the breakpoint then its a gdb problem and should be reported to gdb. (or if you get an error when executing the break command)
Comment 4 Alexander GALANIN 2007-08-20 19:47:32 UTC 
Yes, it looks like a problem in dgb.

Thank you.