pdumper: M-x profiler-start crashes

pdumper: M-x profiler-start crashes

[T.V Raman]

Built from  the pdumper branch and was using the result -- then I
noticed some sluggishness with emacspeak and wanted to see what was
happening.
M-x profiler-start RET cpu RET immediately crashes emacs.

-- 

-- 

-- 

Re: pdumper: M-x profiler-start crashes

[Eli Zaretskii]

> Date: Thu, 15 Feb 2018 18:18:10 -0800
> From: raman@google.com (T.V Raman)
> 
> Built from  the pdumper branch and was using the result -- then I
> noticed some sluggishness with emacspeak and wanted to see what was
> happening.
> M-x profiler-start RET cpu RET immediately crashes emacs.

Can you please run this under a debugger and show the full backtrace
from the crash?  It is usually better to do that in an unoptimized
build, because otherwise backtraces could mislead.

Thanks.

Re: pdumper: M-x profiler-start crashes

[martin rudalics]

 >> M-x profiler-start RET cpu RET immediately crashes emacs.
 >
 > Can you please run this under a debugger and show the full backtrace
 > from the crash?  It is usually better to do that in an unoptimized
 > build, because otherwise backtraces could mislead.

Here (on Windows XP) it gets me

(gdb) bt
#0  0x00000000 in ?? ()
#1  0x011c2fa8 in hash_lookup (h=0x64f52a8, key=XIL(0x6624dbd), hash=0x68bfea0) at ../../src/fns.c:3978
#2  0x012277fa in record_backtrace (log=0x64f52a8, count=1) at ../../src/profiler.c:157
#3  0x0122797e in handle_profiler_signal (sys_signal=19) at ../../src/profiler.c:252
#4  0x0112a8e7 in deliver_process_signal (sig=19, handler=0x12278e5 <handle_profiler_signal>) at ../../src/sysdep.c:1713
#5  0x0122799d in deliver_profiler_signal (sys_signal=19) at ../../src/profiler.c:259
#6  0x012735c3 in timer_loop (arg=0x22e4800 <prof_itimer>) at ../../src/w32proc.c:490
#7  0x7c80b683 in KERNEL32!GetModuleFileNameA () from C:\WINDOWS\system32\kernel32.dll
#8  0x00000000 in ?? ()

Lisp Backtrace:
"file-remote-p" (0x82b89c)
"redisplay_internal (C function)" (0x0)
"redisplay" (0x82eac4)
"sit-for" (0x82edbc)
"execute-extended-command" (0x82f248)
"funcall-interactively" (0x82f244)
"call-interactively" (0x82f4f0)
"command-execute" (0x82f82c)

martin

Re: pdumper: M-x profiler-start crashes

[T.V Raman]

martin rudalics <rudalics@gmx.at> writes:

Thanks for running that under GDB --- I was about to ask for volunteers
since Emacs is what talks to me, so running it under gdb does me little
good since I  wouldn't  get any speech output once I fall into GDB >>> M-x profiler-start RET cpu RET immediately crashes emacs.
>>
>> Can you please run this under a debugger and show the full backtrace
>> from the crash?  It is usually better to do that in an unoptimized
>> build, because otherwise backtraces could mislead.
>
> Here (on Windows XP) it gets me
>
> (gdb) bt
> #0  0x00000000 in ?? ()
> #1  0x011c2fa8 in hash_lookup (h=0x64f52a8, key=XIL(0x6624dbd), hash=0x68bfea0) at ../../src/fns.c:3978
> #2  0x012277fa in record_backtrace (log=0x64f52a8, count=1) at ../../src/profiler.c:157
> #3  0x0122797e in handle_profiler_signal (sys_signal=19) at ../../src/profiler.c:252
> #4  0x0112a8e7 in deliver_process_signal (sig=19, handler=0x12278e5 <handle_profiler_signal>) at ../../src/sysdep.c:1713
> #5  0x0122799d in deliver_profiler_signal (sys_signal=19) at ../../src/profiler.c:259
> #6  0x012735c3 in timer_loop (arg=0x22e4800 <prof_itimer>) at ../../src/w32proc.c:490
> #7  0x7c80b683 in KERNEL32!GetModuleFileNameA () from C:\WINDOWS\system32\kernel32.dll
> #8  0x00000000 in ?? ()
>
> Lisp Backtrace:
> "file-remote-p" (0x82b89c)
> "redisplay_internal (C function)" (0x0)
> "redisplay" (0x82eac4)
> "sit-for" (0x82edbc)
> "execute-extended-command" (0x82f248)
> "funcall-interactively" (0x82f244)
> "call-interactively" (0x82f4f0)
> "command-execute" (0x82f82c)
>
> martin
>

-- 

Re: pdumper: M-x profiler-start crashes

[Stefan Monnier]

> Thanks for running that under GDB --- I was about to ask for volunteers
> since Emacs is what talks to me, so running it under gdb does me little
> good since I  wouldn't  get any speech output once I fall into GDB >>> M-x

FWIW, I always run my main Emacs session from GDB, and that GDB is
always running from an(other) Emacs session ;-)


        Stefan