[Bug gdb/21963] gdb can't work on winpty

[Bug gdb/21963] gdb can't work on winpty

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #1 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Yasuhiro Matsumoto from comment #0)
> So when I try to run gdb with tui mode, winpty fail to open CONOUT$.
>
> I could reproduce with following operation.
> 
> 1. open vim.exe or gvim.exe
> 2. :terminal on vim
> 3. start gdb
> 4. type ^X^A

I just tried these exact steps, and everything seems to work fine.
Do you still have this problem?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/21963] gdb can't work on winpty

[mattn.jp at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

--- Comment #2 from Yasuhiro Matsumoto <mattn.jp at gmail dot com> ---
Yes, I've never seen this problem fixed in two years.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/21963] gdb can't work on winpty

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

--- Comment #3 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Yasuhiro Matsumoto from comment #2)
> Yes, I've never seen this problem fixed in two years.

What is the exact problem you have, because it seems to work just fine for me.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/21963] gdb can't work on winpty

[mattn.jp at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

--- Comment #4 from Yasuhiro Matsumoto <mattn.jp at gmail dot com> ---
Probably, your way to reproduce is different from mine.

1. open vim.exe
2. :set termwintype=winpty
2. :terminal
3. start gdb in the terminal
4. type ^X^A

gdb should start tui mode. But gdb crash always.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/21963] gdb can't work on winpty

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

--- Comment #5 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Yasuhiro Matsumoto from comment #4)
> Probably, your way to reproduce is different from mine.
> 
> 1. open vim.exe
> 2. :set termwintype=winpty
> 2. :terminal
> 3. start gdb in the terminal
> 4. type ^X^A
> 
> gdb should start tui mode. But gdb crash always.

No crash for me here also, I could even debug in the gdb TUI.
But maybe it's because I compiled with pdcurses.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/21963] gdb can't work on winpty

[mattn.jp at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

--- Comment #6 from Yasuhiro Matsumoto <mattn.jp at gmail dot com> ---
I don't know how the pdcurses build you used affects this bug, but it's true
that it can't access the console on Windows without FILE_SHARE_WRITE, which
triggers the bug.

https://github.com/bminor/binutils-gdb/blob/0749542484129e77a30f1089d6d671197be5035f/gdb/windows-nat.c#L2059-L2060

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/21963] gdb can't work on winpty

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=21963

--- Comment #7 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Yasuhiro Matsumoto from comment #6)
> I don't know how the pdcurses build you used affects this bug, but it's true
> that it can't access the console on Windows without FILE_SHARE_WRITE, which
> triggers the bug.
> 
> https://github.com/bminor/binutils-gdb/blob/
> 0749542484129e77a30f1089d6d671197be5035f/gdb/windows-nat.c#L2059-L2060

I don't think this is the problem code that made your gdb crash, because this
is only called when gdb creates a new inferior process.

-- 
You are receiving this mail because:
You are on the CC list for the bug.