Re: [RFC] Fix problems related to Mingw/DJGPP file names containing colons

[Keith Seitz <keiths@redhat.com>]

On 08/12/2011 08:50 AM, Pierre Muller wrote:
>    I first tried to add double-quotes around the file name,
> but this was not enough... I suspect that the other changes
> below that I had to add are just errors in the current implementation...
>    See below for submitted patch.

I remember this bug. I believe I introduced this with one of my many 
hackings on linespec.c. This is gdb/12843, about which I'd nearly forgotten.

I was going to work on this patch after 12266, but that bug has lasted 
much longer than I expected.

Unfortunately, your patch causes several test suite regressions for me 
(as it is right now):

+FAIL: gdb.base/break.exp: breakpoint quoted function (got interactive 
prompt)
+FAIL: gdb.base/break.exp: breakpoint info
+FAIL: gdb.base/break.exp: info break 2 4 6
+FAIL: gdb.base/break.exp: info break 3-5
+FAIL: gdb.base/break.exp: check disable with history values
+FAIL: gdb.base/break.exp: check disable with convenience values
+FAIL: gdb.base/break.exp: run until quoted breakpoint
+FAIL: gdb.base/break.exp: run until file:linenum breakpoint (the 
program exited)
+FAIL: gdb.base/break.exp: step onto breakpoint (the program is no 
longer running)
+FAIL: gdb.base/break.exp: continue to breakpoint at } (the program is 
no longer running)
+FAIL: gdb.base/sepdebug.exp: breakpoint quoted function (got 
interactive prompt)
+FAIL: gdb.base/sepdebug.exp: breakpoint info
+FAIL: gdb.base/sepdebug.exp: run until quoted breakpoint
+FAIL: gdb.base/sepdebug.exp: run until file:linenum breakpoint (the 
program exited)
+FAIL: gdb.base/sepdebug.exp: step onto breakpoint (the program is no 
+FAIL: gdb.cp/cmpd-minsyms.exp: setting breakpoint at "int 
GDB<char>::even_harder<int>(char)"
+FAIL: gdb.cp/overload.exp: list overloaded function with function ptr 
args - quotes around argument

If it's okay with you, I'd like to take this bug myself. I will drop 
everything and work on it immediately.

Keith