Hello,
On Sun, 12 Jun 2005, Krzysztof Duleba wrote:
> Yes, that's it! mcedit failes after F10 if I used Ctrl + O earlier.
> Sometimes it's not even a stackdump, but an infinite loop with 100% CPU
> usage.
>
> > In any case - please try
> > using the user menu and then quit to see if you'll manage
Pavel Tsekov wrote:
> > > I am pretty confident that I've found the cause for the crash. It is
> > > indeed a double free issue as Christopher Faylor suggested. I just
want
> > a
> > > confirmation from you if it is possible - does the crash happen only
if
> > > you use the 'User Menu' (F11) in th
Hello,
On Sun, 12 Jun 2005, Krzysztof Duleba wrote:
> Pavel Tsekov wrote:
>
> > > For a few months now I've been suffering from mcedit internal error.
> Every
> > > once in a while, without any reason, mcedit stackdumps during exit
> > > procedure (afte
Pavel Tsekov wrote:
> > For a few months now I've been suffering from mcedit internal error.
Every
> > once in a while, without any reason, mcedit stackdumps during exit
> > procedure (after pressing F10 or double ESC). I got this error with
> > 1.5.16, then with 1
Hello,
On Fri, 10 Jun 2005, Krzysztof Duleba wrote:
> For a few months now I've been suffering from mcedit internal error. Every
> once in a while, without any reason, mcedit stackdumps during exit
> procedure (after pressing F10 or double ESC). I got this error with
> 1.5.16,
Pavel Tsekov wrote:
> > For a few months now I've been suffering from mcedit internal error.
> > Every once in a while, without any reason, mcedit stackdumps during
> > exit procedure (after pressing F10 or double ESC). I got this error
> > with 1.5.16, then with 1
Hello,
On Fri, 10 Jun 2005, Krzysztof Duleba wrote:
> Hi
>
> For a few months now I've been suffering from mcedit internal error. Every
> once in a while, without any reason, mcedit stackdumps during exit
> procedure (after pressing F10 or double ESC). I got this error with
I read the mailing list every day. MC on Cygwin does not lack a maintainer.
I'll try my best to solve this issue.
-- оригин. съобщ. --
Тема: Re: mcedit stackdumps (Pavel please comment?)
От: Christopher Faylor
Two things:
- It would be nice if the mc maintainer would comment on
Hello,
On Fri, 10 Jun 2005, Krzysztof Duleba wrote:
> Christopher Faylor wrote:
>
> > >$ cat mc.exe.stackdump
> > >Exception: STATUS_ACCESS_VIOLATION at eip=610CA032
> >
> > This is indicative of a malloc corruption problem. It is probably a
> problem
> > with mcedit itself, not cygwin.
>
> OK,
On Fri, Jun 10, 2005 at 12:25:38PM -0400, Christopher Faylor wrote:
>- This is problem is usually caused by free()ing the same block of memory
>twice.
Sigh. To restate in English:
"This problem is usually caused by free()ing the same block of memory
twice."
cgf
--
Unsubscribe info: http:/
On Fri, Jun 10, 2005 at 06:19:25PM +0200, Krzysztof Duleba wrote:
>Christopher Faylor wrote:
>
>> >$ cat mc.exe.stackdump
>> >Exception: STATUS_ACCESS_VIOLATION at eip=610CA032
>>
>>This is indicative of a malloc corruption problem. It is probably a
>>problem with mcedit itself, not cygwin.
>
>OK,
Christopher Faylor wrote:
> >$ cat mc.exe.stackdump
> >Exception: STATUS_ACCESS_VIOLATION at eip=610CA032
>
> This is indicative of a malloc corruption problem. It is probably a
problem
> with mcedit itself, not cygwin.
OK, I sent the report to mc mailing list. I hope they will know what to do
a
On Fri, Jun 10, 2005 at 04:47:37PM +0200, Krzysztof Duleba wrote:
>Hi
>
>For a few months now I've been suffering from mcedit internal error. Every
>once in a while, without any reason, mcedit stackdumps during exit
>procedure (after pressing F10 or double ESC). I got this erro
Hi
For a few months now I've been suffering from mcedit internal error. Every
once in a while, without any reason, mcedit stackdumps during exit
procedure (after pressing F10 or double ESC). I got this error with
1.5.16, then with 1.5.17 snapshots, and now with 1.5.17 as well. I haven&#x
14 matches
Mail list logo
