gdb 7.11.1-2 started within emacs fails

gdb 7.11.1-2 started within emacs fails

[Rockefeller, Harry]

Using program foo:
      program foo
      e = 1.0
      stop
      end

$ /usr/bin/gfortran    -g foo.f -o foo

Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 3.18.9) of 2016-09-17

Inside emacs I ran M-x gud-gdb and got
... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
(gdb) b 1
Breakpoint 1 at 0x4011d6: file foo.f, line 1.
(gdb) r
Starting program: /cygdrive/c/Users/harryr/foo.exe
[New Thread 6296.0x22ac]
[New Thread 6296.0x24d4]
readline: readline_callback_read_char() called with no handler!
Debugger aborted (core dumped)

Foo written in C++ also fails with the same message.
Running gdb foo in bash gives the expected result:
gdb stops at first executable line prompting for next gdb command.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[Ken Brown]

On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
> Using program foo:
>       program foo
>       e = 1.0
>       stop
>       end
>
> $ /usr/bin/gfortran    -g foo.f -o foo
>
> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 3.18.9) of 2016-09-17
>
> Inside emacs I ran M-x gud-gdb and got
> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
> (gdb) b 1
> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
> (gdb) r
> Starting program: /cygdrive/c/Users/harryr/foo.exe
> [New Thread 6296.0x22ac]
> [New Thread 6296.0x24d4]
> readline: readline_callback_read_char() called with no handler!
> Debugger aborted (core dumped)
>
> Foo written in C++ also fails with the same message.
> Running gdb foo in bash gives the expected result:
> gdb stops at first executable line prompting for next gdb command.

I can confirm that this happens also with gdb-7.11.1-1 but not 
gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)

It also fails with M-x gdb instead of M-x gud-gdb, but with a different 
error message:

   Failed to resume program execution (ContinueDebugEvent failed, error 87)

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: gdb 7.11.1-2 started within emacs fails

[Rockefeller, Harry]

>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of Ken Brown
>Sent: Tuesday, September 27, 2016 3:16 PM
>To: cygwin@cygwin.com
>Subject: Re: gdb 7.11.1-2 started within emacs fails

>On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>> Using program foo:
>>       program foo
>>       e = 1.0
>>       stop
>>       end
>>
>> $ /usr/bin/gfortran    -g foo.f -o foo
>>
>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version
>> 3.18.9) of 2016-09-17
>>
>> Inside emacs I ran M-x gud-gdb and got ... GNU gdb (GDB) (Cygwin
>> 7.11.1-2) 7.11.1 ...
>> (gdb) b 1
>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>> (gdb) r
>> Starting program: /cygdrive/c/Users/harryr/foo.exe [New Thread
>> 6296.0x22ac] [New Thread 6296.0x24d4]
>> readline: readline_callback_read_char() called with no handler!
>> Debugger aborted (core dumped)
>>
>> Foo written in C++ also fails with the same message.
>> Running gdb foo in bash gives the expected result:
>> gdb stops at first executable line prompting for next gdb command.
>I can confirm that this happens also with gdb-7.11.1-1 but not gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
>It also fails with M-x gdb instead of M-x gud-gdb, but with a different error message:
>Failed to resume program execution (ContinueDebugEvent failed, error 87)
>Ken

I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[William M. (Mike) Miller]

On Thu, Sep 29, 2016 at 11:21 AM, Rockefeller, Harry
<Harry.Rockefeller@flightsafety.com> wrote:
>
>>-----Original Message-----
>>From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of Ken Brown
>>Sent: Tuesday, September 27, 2016 3:16 PM
>>To: cygwin@cygwin.com
>>Subject: Re: gdb 7.11.1-2 started within emacs fails
>
>>On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>>> Using program foo:
>>>       program foo
>>>       e = 1.0
>>>       stop
>>>       end
>>>
>>> $ /usr/bin/gfortran    -g foo.f -o foo
>>>
>>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version
>>> 3.18.9) of 2016-09-17
>>>
>>> Inside emacs I ran M-x gud-gdb and got ... GNU gdb (GDB) (Cygwin
>>> 7.11.1-2) 7.11.1 ...
>>> (gdb) b 1
>>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>>> (gdb) r
>>> Starting program: /cygdrive/c/Users/harryr/foo.exe [New Thread
>>> 6296.0x22ac] [New Thread 6296.0x24d4]
>>> readline: readline_callback_read_char() called with no handler!
>>> Debugger aborted (core dumped)
>>>
>>> Foo written in C++ also fails with the same message.
>>> Running gdb foo in bash gives the expected result:
>>> gdb stops at first executable line prompting for next gdb command.
>>I can confirm that this happens also with gdb-7.11.1-1 but not gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
>>It also fails with M-x gdb instead of M-x gud-gdb, but with a different error message:
>>Failed to resume program execution (ContinueDebugEvent failed, error 87)
>>Ken
>
> I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.

Any progress on the above issue? I recently updated my gdb and am
running into the same problem.

-- 
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: gdb 7.11.1-2 started within emacs fails

[Rockefeller, Harry]

>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of William M. (Mike) Miller
>Sent: Wednesday, October 19, 2016 10:30 AM
>To: cygwin@cygwin.com
>Subject: Re: gdb 7.11.1-2 started within emacs fails
[snip]
>>>I can confirm that this happens also with gdb-7.11.1-1 but not
>>>gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
>>>It also fails with M-x gdb instead of M-x gud-gdb, but with a different error message:
>>>Failed to resume program execution (ContinueDebugEvent failed, error
>>>87) Ken
>>
>> I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.

>Any progress on the above issue? I recently updated my gdb and am running into the same problem.
>William M. (Mike) Miller | Edison Design Group william.m.miller@gmail.com

No progress I am aware of.  I switched over to 64-bit Cygwin which uses gdb-7.10.1-1 to avoid this problem.
This "request" may be related to the problem: I would like to see the autogenerated gdb line:
"---Type <return> to continue, or q <return> to quit---" to go away.
gdb pauses posting this line unnecessarily.

Re: gdb 7.11.1-2 started within emacs fails

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On Oct 19 12:46, Rockefeller, Harry wrote:
> >-----Original Message-----
> >From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of William M. (Mike) Miller
> >Sent: Wednesday, October 19, 2016 10:30 AM
> >To: cygwin@cygwin.com
> >Subject: Re: gdb 7.11.1-2 started within emacs fails
> [snip]
> >>>I can confirm that this happens also with gdb-7.11.1-1 but not
> >>>gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
> >>>It also fails with M-x gdb instead of M-x gud-gdb, but with a different error message:
> >>>Failed to resume program execution (ContinueDebugEvent failed, error
> >>>87) Ken
> >>
> >> I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.
> 
> >Any progress on the above issue? I recently updated my gdb and am running into the same problem.
> >William M. (Mike) Miller | Edison Design Group william.m.miller@gmail.com
> 
> No progress I am aware of.  I switched over to 64-bit Cygwin which uses gdb-7.10.1-1 to avoid this problem.
> This "request" may be related to the problem: I would like to see the autogenerated gdb line:
> "---Type <return> to continue, or q <return> to quit---" to go away.
> gdb pauses posting this line unnecessarily.

https://sourceware.org/gdb/wiki/FAQ#How_do_I_disable_the_.22Type_.3Creturn.3E_to_continue.2C_or_q_.3Creturn.3E_to_quit.22_pagination_prompt_in_GDB.3F


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: gdb 7.11.1-2 started within emacs fails

[William M. (Mike) Miller]

On Wed, Oct 19, 2016 at 12:54 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Oct 19 12:46, Rockefeller, Harry wrote:
>> >-----Original Message-----
>> >From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of William M. (Mike) Miller
>> >Sent: Wednesday, October 19, 2016 10:30 AM
>> >To: cygwin@cygwin.com
>> >Subject: Re: gdb 7.11.1-2 started within emacs fails
>> [snip]
>> >>>I can confirm that this happens also with gdb-7.11.1-1 but not
>> >>>gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
>> >>>It also fails with M-x gdb instead of M-x gud-gdb, but with a different error message:
>> >>>Failed to resume program execution (ContinueDebugEvent failed, error
>> >>>87) Ken
>> >>
>> >> I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.
>>
>> >Any progress on the above issue? I recently updated my gdb and am running into the same problem.
>> >William M. (Mike) Miller | Edison Design Group william.m.miller@gmail.com
>>
>> No progress I am aware of.  I switched over to 64-bit Cygwin which uses gdb-7.10.1-1 to avoid this problem.
>> This "request" may be related to the problem: I would like to see the autogenerated gdb line:
>> "---Type <return> to continue, or q <return> to quit---" to go away.
>> gdb pauses posting this line unnecessarily.
>
> https://sourceware.org/gdb/wiki/FAQ#How_do_I_disable_the_.22Type_.3Creturn.3E_to_continue.2C_or_q_.3Creturn.3E_to_quit.22_pagination_prompt_in_GDB.3F

Thanks for the reference. I don't know why the OP thought that might
have been related to the gdb crash, but it didn't do anything to help
with that when I tried it.

-- 
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[Jon Turney]

On 19/10/2016 17:46, Rockefeller, Harry wrote:
>>>> I can confirm that this happens also with gdb-7.11.1-1 but not
>>>> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
>>>> It also fails with M-x gdb instead of M-x gud-gdb, but with a different error message:
>>>> Failed to resume program execution (ContinueDebugEvent failed, error
>>>> 87) Ken
>>>
>>> I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.
>
>> Any progress on the above issue? I recently updated my gdb and am running into the same problem.
>
> No progress I am aware of.  I switched over to 64-bit Cygwin which uses gdb-7.10.1-1 to avoid this problem.

I've done some investigation, and the problem seems to be that when run 
from emacs or ddd, the inferior process doesn't end up in it's own 
process group, but I haven't made any progress on why that is happening.

per [1], I think I've fixed the problem with x86 and gdb-7.10.1-1, so it 
should no longer be necessary to use gdb-7.11.1 to avoid those problems, 
but obviously this needs to be fixed at some point...

[1] https://cygwin.com/ml/cygwin/2016-10/msg00243.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[Jon Turney]

On 27/09/2016 21:15, Ken Brown wrote:
> On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>> Using program foo:
>>       program foo
>>       e = 1.0
>>       stop
>>       end
>>
>> $ /usr/bin/gfortran    -g foo.f -o foo
>>
>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 
>> 3.18.9) of 2016-09-17
>>
>> Inside emacs I ran M-x gud-gdb and got
>> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
>> (gdb) b 1
>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>> (gdb) r
>> Starting program: /cygdrive/c/Users/harryr/foo.exe
>> [New Thread 6296.0x22ac]
>> [New Thread 6296.0x24d4]
>> readline: readline_callback_read_char() called with no handler!
>> Debugger aborted (core dumped)
>>
>> Foo written in C++ also fails with the same message.
>> Running gdb foo in bash gives the expected result:
>> gdb stops at first executable line prompting for next gdb command.
> 
> I can confirm that this happens also with gdb-7.11.1-1 but not 
> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
> 
> It also fails with M-x gdb instead of M-x gud-gdb, but with a different 
> error message:
> 
>    Failed to resume program execution (ContinueDebugEvent failed, error 87)

These problem seem not longer occur due to upstream changes in gdb 7.12.

I've uploaded a gdb 7.12.1-1 test package.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[Ken Brown]

On 10/11/2017 3:44 PM, Jon Turney wrote:
> On 27/09/2016 21:15, Ken Brown wrote:
>> On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>>> Using program foo:
>>>       program foo
>>>       e = 1.0
>>>       stop
>>>       end
>>>
>>> $ /usr/bin/gfortran    -g foo.f -o foo
>>>
>>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 
>>> 3.18.9) of 2016-09-17
>>>
>>> Inside emacs I ran M-x gud-gdb and got
>>> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
>>> (gdb) b 1
>>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>>> (gdb) r
>>> Starting program: /cygdrive/c/Users/harryr/foo.exe
>>> [New Thread 6296.0x22ac]
>>> [New Thread 6296.0x24d4]
>>> readline: readline_callback_read_char() called with no handler!
>>> Debugger aborted (core dumped)
>>>
>>> Foo written in C++ also fails with the same message.
>>> Running gdb foo in bash gives the expected result:
>>> gdb stops at first executable line prompting for next gdb command.
>>
>> I can confirm that this happens also with gdb-7.11.1-1 but not 
>> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
>>
>> It also fails with M-x gdb instead of M-x gud-gdb, but with a 
>> different error message:
>>
>>    Failed to resume program execution (ContinueDebugEvent failed, 
>> error 87)
> 
> These problem seem not longer occur due to upstream changes in gdb 7.12.

Everything seems fine on x86_64 and with M-x gud-gdb on x86.  But when I 
run M-x gdb on x86 (even with no file), gdb crashes.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[Jon Turney]

On 11/10/2017 21:32, Ken Brown wrote:
> On 10/11/2017 3:44 PM, Jon Turney wrote:
>> On 27/09/2016 21:15, Ken Brown wrote:
>>> On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>>>> Using program foo:
>>>>       program foo
>>>>       e = 1.0
>>>>       stop
>>>>       end
>>>>
>>>> $ /usr/bin/gfortran    -g foo.f -o foo
>>>>
>>>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 
>>>> 3.18.9) of 2016-09-17
>>>>
>>>> Inside emacs I ran M-x gud-gdb and got
>>>> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
>>>> (gdb) b 1
>>>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>>>> (gdb) r
>>>> Starting program: /cygdrive/c/Users/harryr/foo.exe
>>>> [New Thread 6296.0x22ac]
>>>> [New Thread 6296.0x24d4]
>>>> readline: readline_callback_read_char() called with no handler!
>>>> Debugger aborted (core dumped)
>>>>
>>>> Foo written in C++ also fails with the same message.
>>>> Running gdb foo in bash gives the expected result:
>>>> gdb stops at first executable line prompting for next gdb command.
>>>
>>> I can confirm that this happens also with gdb-7.11.1-1 but not 
>>> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on 
>>> x86.)
>>>
>>> It also fails with M-x gdb instead of M-x gud-gdb, but with a 
>>> different error message:
>>>
>>>    Failed to resume program execution (ContinueDebugEvent failed, 
>>> error 87)
>>
>> These problem seem not longer occur due to upstream changes in gdb 7.12.
> 
> Everything seems fine on x86_64 and with M-x gud-gdb on x86.  But when I 
> run M-x gdb on x86 (even with no file), gdb crashes.

Thanks for testing.

It seems this issue is known [1], so I made a gdb 7.12.1-2 with the 
work-around from there applied, which seems to fix M-x gdb on x86.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=21078


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: gdb 7.11.1-2 started within emacs fails

[Ken Brown]

On 10/12/2017 1:24 PM, Jon Turney wrote:
> On 11/10/2017 21:32, Ken Brown wrote:
>> On 10/11/2017 3:44 PM, Jon Turney wrote:
>>> On 27/09/2016 21:15, Ken Brown wrote:
>>>> On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>>>>> Using program foo:
>>>>>       program foo
>>>>>       e = 1.0
>>>>>       stop
>>>>>       end
>>>>>
>>>>> $ /usr/bin/gfortran    -g foo.f -o foo
>>>>>
>>>>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 
>>>>> 3.18.9) of 2016-09-17
>>>>>
>>>>> Inside emacs I ran M-x gud-gdb and got
>>>>> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
>>>>> (gdb) b 1
>>>>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>>>>> (gdb) r
>>>>> Starting program: /cygdrive/c/Users/harryr/foo.exe
>>>>> [New Thread 6296.0x22ac]
>>>>> [New Thread 6296.0x24d4]
>>>>> readline: readline_callback_read_char() called with no handler!
>>>>> Debugger aborted (core dumped)
>>>>>
>>>>> Foo written in C++ also fails with the same message.
>>>>> Running gdb foo in bash gives the expected result:
>>>>> gdb stops at first executable line prompting for next gdb command.
>>>>
>>>> I can confirm that this happens also with gdb-7.11.1-1 but not 
>>>> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on 
>>>> x86.)
>>>>
>>>> It also fails with M-x gdb instead of M-x gud-gdb, but with a 
>>>> different error message:
>>>>
>>>>    Failed to resume program execution (ContinueDebugEvent failed, 
>>>> error 87)
>>>
>>> These problem seem not longer occur due to upstream changes in gdb 7.12.
>>
>> Everything seems fine on x86_64 and with M-x gud-gdb on x86.  But when 
>> I run M-x gdb on x86 (even with no file), gdb crashes.
> 
> Thanks for testing.
> 
> It seems this issue is known [1], so I made a gdb 7.12.1-2 with the 
> work-around from there applied, which seems to fix M-x gdb on x86.

Confirmed.

Thanks.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple