Ryan Johnson | 1 May 2012 03:07
Picon
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 30/04/2012 8:48 PM, Ryan Johnson wrote:
> On 30/04/2012 4:08 PM, Ken Brown wrote:
>> Test releases of the emacs, emacs-X11, and emacs-el packages 
>> (24.0.96-1) are now available.  This is a pretest for the upcoming 
>> release of emacs-24.1.
>>
>> Emacs users are encouraged to try it and report any problems to the 
>> cygwin mailing list.
> I'm experiencing regular seg faults, often while using gdb but not 
> always (switching between buffers is another big offender). I'm not 
> sure what other information I can provide, other than the EIP=610CF707 
> reported in the .stackdump file...
Caught one in gdb (no symbols, sadly):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8128.0x3d0]
0x0000010c in ?? ()
(gdb) bt
#0  0x0000010c in ?? ()
#1  0x0054b0ac in ?? ()
#2  0x004e4303 in ?? ()
#3  0x0054afbe in ?? ()
#4  0x004e4e96 in ?? ()
#5  0x004e5180 in ?? ()
#6  0x004dfbec in ?? ()
#7  0x610070d8 in _cygwin_exit_return () from /usr/bin/cygwin1.dll
#8  0x00000003 in ?? ()
#9  0x610050dd in _cygtls::call2(unsigned long (*)(void*, void*), void*, 
void*)
     () from /usr/bin/cygwin1.dll
(Continue reading)

Ken Brown | 1 May 2012 04:08
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 4/30/2012 9:07 PM, Ryan Johnson wrote:
> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>> release of emacs-24.1.
>>>
>>> Emacs users are encouraged to try it and report any problems to the
>>> cygwin mailing list.
>> I'm experiencing regular seg faults, often while using gdb but not
>> always (switching between buffers is another big offender). I'm not
>> sure what other information I can provide, other than the EIP=610CF707
>> reported in the .stackdump file...
> Caught one in gdb (no symbols, sadly):
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 8128.0x3d0]
> 0x0000010c in ?? ()
> (gdb) bt
> #0 0x0000010c in ?? ()
> #1 0x0054b0ac in ?? ()
> #2 0x004e4303 in ?? ()
> #3 0x0054afbe in ?? ()
> #4 0x004e4e96 in ?? ()
> #5 0x004e5180 in ?? ()
> #6 0x004dfbec in ?? ()
> #7 0x610070d8 in _cygwin_exit_return () from /usr/bin/cygwin1.dll
> #8 0x00000003 in ?? ()
> #9 0x610050dd in _cygtls::call2(unsigned long (*)(void*, void*), void*,
> void*)
(Continue reading)

Ryan Johnson | 1 May 2012 05:52
Picon
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 30/04/2012 10:08 PM, Ken Brown wrote:
> On 4/30/2012 9:07 PM, Ryan Johnson wrote:
>> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>>> release of emacs-24.1.
>>>>
>>>> Emacs users are encouraged to try it and report any problems to the
>>>> cygwin mailing list.
>>> I'm experiencing regular seg faults, often while using gdb but not
>>> always (switching between buffers is another big offender). I'm not
>>> sure what other information I can provide, other than the EIP=610CF707
>>> reported in the .stackdump file...
>> Caught one in gdb (no symbols, sadly):
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 8128.0x3d0]
>> 0x0000010c in ?? ()
>> (gdb) bt
>> #0 0x0000010c in ?? ()
>> #1 0x0054b0ac in ?? ()
>> #2 0x004e4303 in ?? ()
>> #3 0x0054afbe in ?? ()
>> #4 0x004e4e96 in ?? ()
>> #5 0x004e5180 in ?? ()
>> #6 0x004dfbec in ?? ()
>> #7 0x610070d8 in _cygwin_exit_return () from /usr/bin/cygwin1.dll
>> #8 0x00000003 in ?? ()
>> #9 0x610050dd in _cygtls::call2(unsigned long (*)(void*, void*), void*,
(Continue reading)

Ken Brown | 2 May 2012 15:55
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 4/30/2012 11:52 PM, Ryan Johnson wrote:
> On 30/04/2012 10:08 PM, Ken Brown wrote:
>> On 4/30/2012 9:07 PM, Ryan Johnson wrote:
>>> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>>>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>>>> release of emacs-24.1.
>>>>>
>>>>> Emacs users are encouraged to try it and report any problems to the
>>>>> cygwin mailing list.
>>>> I'm experiencing regular seg faults, often while using gdb but not
>>>> always (switching between buffers is another big offender). I'm not
>>>> sure what other information I can provide, other than the EIP=610CF707
>>>> reported in the .stackdump file...
>>> Caught one in gdb (no symbols, sadly):
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> [Switching to Thread 8128.0x3d0]
>>> 0x0000010c in ?? ()
>>> (gdb) bt
>>> #0 0x0000010c in ?? ()
>>> #1 0x0054b0ac in ?? ()
>>> #2 0x004e4303 in ?? ()
>>> #3 0x0054afbe in ?? ()
>>> #4 0x004e4e96 in ?? ()
>>> #5 0x004e5180 in ?? ()
>>> #6 0x004dfbec in ?? ()
>>> #7 0x610070d8 in _cygwin_exit_return () from /usr/bin/cygwin1.dll
>>> #8 0x00000003 in ?? ()
(Continue reading)

Ryan Johnson | 2 May 2012 19:16
Picon
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 02/05/2012 9:55 AM, Ken Brown wrote:
> On 4/30/2012 11:52 PM, Ryan Johnson wrote:
>> On 30/04/2012 10:08 PM, Ken Brown wrote:
>>> On 4/30/2012 9:07 PM, Ryan Johnson wrote:
>>>> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>>>>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>>>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>>>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>>>>> release of emacs-24.1.
>>>>>>
>>>>>> Emacs users are encouraged to try it and report any problems to the
>>>>>> cygwin mailing list.
>>>>> I'm experiencing regular seg faults, often while using gdb but not
>>>>> always (switching between buffers is another big offender). I'm not
>>>>> sure what other information I can provide, other than the 
>>>>> EIP=610CF707
>>>>> reported in the .stackdump file...
>>>> Caught one in gdb (no symbols, sadly):
>>>>
>>>> Program received signal SIGSEGV, Segmentation fault.
>>>> [Switching to Thread 8128.0x3d0]
>>>> 0x0000010c in ?? ()
>>>> (gdb) bt
>>>> #0 0x0000010c in ?? ()
>>>> #1 0x0054b0ac in ?? ()
>>>> #2 0x004e4303 in ?? ()
>>>> #3 0x0054afbe in ?? ()
>>>> #4 0x004e4e96 in ?? ()
>>>> #5 0x004e5180 in ?? ()
>>>> #6 0x004dfbec in ?? ()
(Continue reading)

Ryan Johnson | 2 May 2012 23:02
Picon
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 02/05/2012 1:16 PM, Ryan Johnson wrote:
> On 02/05/2012 9:55 AM, Ken Brown wrote:
>> On 4/30/2012 11:52 PM, Ryan Johnson wrote:
>>> On 30/04/2012 10:08 PM, Ken Brown wrote:
>>>> On 4/30/2012 9:07 PM, Ryan Johnson wrote:
>>>>> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>>>>>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>>>>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>>>>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>>>>>> release of emacs-24.1.
>>>>>>>
>>>>>>> Emacs users are encouraged to try it and report any problems to the
>>>>>>> cygwin mailing list.
>>>>>> I'm experiencing regular seg faults, often while using gdb but not
>>>>>> always (switching between buffers is another big offender). I'm not
>>>>>> sure what other information I can provide, other than the 
>>>>>> EIP=610CF707
>>>>>> reported in the .stackdump file...
>>>>> Caught one in gdb (no symbols, sadly):
>>>>>
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> [Switching to Thread 8128.0x3d0]
>>>>> 0x0000010c in ?? ()
>>>>> (gdb) bt
>>>>> #0 0x0000010c in ?? ()
>>>>> #1 0x0054b0ac in ?? ()
>>>>> #2 0x004e4303 in ?? ()
>>>>> #3 0x0054afbe in ?? ()
>>>>> #4 0x004e4e96 in ?? ()
>>>>> #5 0x004e5180 in ?? ()
(Continue reading)

Ken Brown | 3 May 2012 16:45
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 5/2/2012 5:02 PM, Ryan Johnson wrote:
> On 02/05/2012 1:16 PM, Ryan Johnson wrote:
>> On 02/05/2012 9:55 AM, Ken Brown wrote:
>>> On 4/30/2012 11:52 PM, Ryan Johnson wrote:
>>>> On 30/04/2012 10:08 PM, Ken Brown wrote:
>>>>> On 4/30/2012 9:07 PM, Ryan Johnson wrote:
>>>>>> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>>>>>>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>>>>>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>>>>>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>>>>>>> release of emacs-24.1.
>>>>>>>>
>>>>>>>> Emacs users are encouraged to try it and report any problems to the
>>>>>>>> cygwin mailing list.
>>>>>>> I'm experiencing regular seg faults, often while using gdb but not
>>>>>>> always (switching between buffers is another big offender). I'm not
>>>>>>> sure what other information I can provide, other than the
>>>>>>> EIP=610CF707
>>>>>>> reported in the .stackdump file...
>>>>>> Caught one in gdb (no symbols, sadly):
>>>>>>
>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>> [Switching to Thread 8128.0x3d0]
>>>>>> 0x0000010c in ?? ()
>>>>>> (gdb) bt
>>>>>> #0 0x0000010c in ?? ()
>>>>>> #1 0x0054b0ac in ?? ()
>>>>>> #2 0x004e4303 in ?? ()
>>>>>> #3 0x0054afbe in ?? ()
>>>>>> #4 0x004e4e96 in ?? ()
(Continue reading)

Ryan Johnson | 3 May 2012 22:10
Picon
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 03/05/2012 10:45 AM, Ken Brown wrote:
> On 5/2/2012 5:02 PM, Ryan Johnson wrote:
>> On 02/05/2012 1:16 PM, Ryan Johnson wrote:
>>> On 02/05/2012 9:55 AM, Ken Brown wrote:
>>>> On 4/30/2012 11:52 PM, Ryan Johnson wrote:
>>>>> On 30/04/2012 10:08 PM, Ken Brown wrote:
>>>>>> On 4/30/2012 9:07 PM, Ryan Johnson wrote:
>>>>>>> On 30/04/2012 8:48 PM, Ryan Johnson wrote:
>>>>>>>> On 30/04/2012 4:08 PM, Ken Brown wrote:
>>>>>>>>> Test releases of the emacs, emacs-X11, and emacs-el packages
>>>>>>>>> (24.0.96-1) are now available. This is a pretest for the upcoming
>>>>>>>>> release of emacs-24.1.
>>>>>>>>>
>>>>>>>>> Emacs users are encouraged to try it and report any problems 
>>>>>>>>> to the
>>>>>>>>> cygwin mailing list.
>>>>>>>> I'm experiencing regular seg faults, often while using gdb but not
>>>>>>>> always (switching between buffers is another big offender). I'm 
>>>>>>>> not
>>>>>>>> sure what other information I can provide, other than the
>>>>>>>> EIP=610CF707
>>>>>>>> reported in the .stackdump file...
>>>>>>> Caught one in gdb (no symbols, sadly):
>>>>>>>
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> [Switching to Thread 8128.0x3d0]
>>>>>>> 0x0000010c in ?? ()
>>>>>>> (gdb) bt
>>>>>>> #0 0x0000010c in ?? ()
>>>>>>> #1 0x0054b0ac in ?? ()
(Continue reading)

Ken Brown | 4 May 2012 21:39
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 5/3/2012 4:10 PM, Ryan Johnson wrote:
> On 03/05/2012 10:45 AM, Ken Brown wrote:
>> On 5/2/2012 5:02 PM, Ryan Johnson wrote:
>>> On 02/05/2012 1:16 PM, Ryan Johnson wrote:
>>> The gdb-mi integration also seems to work reasonably well, with a few
>>> exceptions:
[...]
>> (This was fixed once and was a Cygwin bug, so I think it won't be hard
>> for me to resurrect my test case and get it fixed again.)

This is now fixed (http://cygwin.com/ml/cygwin/2012-05/msg00084.html).

>>> One last note: I normally use emacs in terminal mode, but couldn't do
>>> that inside gdb (for obvious reasons). Some of the behaviors I observed
>>> before -- including seg faults -- may be terminal-specific, and some of
>>> the new strangeness I'm pointing out now may be X11-specific... or it
>>> might just be the difference between -O0 and -O2.
>>
>> What do you mean by "terminal mode"? Do you mean you run emacs under
>> mintty? Or do you run it under xterm with the -nw switch? And could
>> you elaborate on the "obvious reasons"? I don't see why you can't run
>> emacs in a terminal under gdb; or attach to it from a different
>> terminal if that's more convenient.
> I usually run under mintty with -nw. When following the instructions in
> that /etc/DEBUG file you pointed me at, the .gdbinit included
> breakpoints and other pre-main intializations to perform that would not
> happen if I merely attached to a running emacs. However, that will
> probably be my next attempt, since the X11 route didn't pan out (and I
> dislike using the graphical version).

(Continue reading)

Ryan Johnson | 5 May 2012 04:12
Picon
Picon
Favicon

Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST)

On 04/05/2012 1:39 PM, Ken Brown wrote:
> On 5/3/2012 4:10 PM, Ryan Johnson wrote:
>> On 03/05/2012 10:45 AM, Ken Brown wrote:
>>> On 5/2/2012 5:02 PM, Ryan Johnson wrote:
>>>> On 02/05/2012 1:16 PM, Ryan Johnson wrote:
>>>> The gdb-mi integration also seems to work reasonably well, with a few
>>>> exceptions:
> [...]
>>> (This was fixed once and was a Cygwin bug, so I think it won't be hard
>>> for me to resurrect my test case and get it fixed again.)
>
> This is now fixed (http://cygwin.com/ml/cygwin/2012-05/msg00084.html).
Ack.

>
>>>> One last note: I normally use emacs in terminal mode, but couldn't do
>>>> that inside gdb (for obvious reasons). Some of the behaviors I 
>>>> observed
>>>> before -- including seg faults -- may be terminal-specific, and 
>>>> some of
>>>> the new strangeness I'm pointing out now may be X11-specific... or it
>>>> might just be the difference between -O0 and -O2.
>>>
>>> What do you mean by "terminal mode"? Do you mean you run emacs under
>>> mintty? Or do you run it under xterm with the -nw switch? And could
>>> you elaborate on the "obvious reasons"? I don't see why you can't run
>>> emacs in a terminal under gdb; or attach to it from a different
>>> terminal if that's more convenient.
>> I usually run under mintty with -nw. When following the instructions in
>> that /etc/DEBUG file you pointed me at, the .gdbinit included
(Continue reading)


Gmane