all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "john naegle" <john.naegle@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, 719@emacsbugs.donarmstrong.com
Subject: bug#719: Crash opening UNC file
Date: Fri, 15 Aug 2008 09:20:12 -0400	[thread overview]
Message-ID: <eb5a18c20808150620u5fc23c24qfe9057048cc1d3bc@mail.gmail.com> (raw)
In-Reply-To: <uiqu2g1ay.fsf@gnu.org>

On a hunch, I commented everything out in my .emacs file and tried to
re-open the file.  I was able to open it without a crash, so I
systematically added things back until I could reproduce the crash.
The culprit turned out to be this line: (require 'rails).

Here are the answers to your questions if you want to pursue this
further.  Let me know if you would like my .emacs file.

Trying to open //server/software/file.txt also crashed.

Here is everything I was able to get out of GDB, it didn't seem that
helpful to me:

Let me know if you want me to try anything else.

This debugging session was started by:

#1) Launching C:\Program Files\emacs-22.2\bin\runemacs.exe
#2) find-file \\server\software\file.txt
#3) Emacs crash dialog presented
#4) gdb -p <pid>

$ gdb -p 2616
GNU gdb 6.5.50.20060706-cvs (cygwin-special)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Attaching to process 2616

[Switching to thread 2616.0x870]
(gdb) info threads
* 3 thread 2616.0x870  0x77f9193d in ntdll!DbgUiConnectToDbg ()
  2 thread 2616.0x984  0x77e585c7 in USER32!GetMenuItemRect ()
  1 thread 2616.0xaac  0x77e58b53 in WaitMessage ()

(gdb) bt full
#0  0x77f9193d in ntdll!DbgUiConnectToDbg ()
No symbol table info available.
#1  0x7c57fecd in KERNEL32!DebugActiveProcess ()
No symbol table info available.
#2  0x7c57b3bc in lstrcmpiW ()
No symbol table info available.
#3  0x00000000 in ?? ()
No symbol table info available.

(gdb) thread 2
[Switching to thread 2 (thread 2616.0x984)]#0  0x77e585c7 in USER32!GetMenuItemR
ect ()
(gdb) bt full
#0  0x77e585c7 in USER32!GetMenuItemRect ()
No symbol table info available.
#1  0x77e1698f in USER32!GetMessageA ()
No symbol table info available.
#2  0x01139207 in ?? ()
No symbol table info available.

(gdb) thread 1
[Switching to thread 1 (thread 2616.0xaac)]#0  0x77e58b53 in WaitMessage ()
(gdb) bt full
#0  0x77e58b53 in WaitMessage ()
No symbol table info available.
#1  0x77e33630 in USER32!MessageBoxA ()
No symbol table info available.
#2  0x77e44327 in USER32!CheckRadioButton ()
No symbol table info available.
#3  0x001008bc in ?? ()
No symbol table info available.


On Fri, Aug 15, 2008 at 3:55 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 14 Aug 2008 11:00:59 -0400
>> From: "john naegle" <john.naegle@gmail.com>
>> Cc:
>>
>> Whenever I try to open a file on a share on another computer, emacs crashes.
>
> Thank you for your report.
>
>> For instance, trying to open the file: "\\server\software\file.txt"
>> causes a crash.  This happens if I use find-file, drag a file onto
>> emacs, or double click to open a file on a hidden network share.
>>
>> If I double-escape all the backslashes, I still get the crash, eg:
>> emacs \\\\server\\software\\file.txt
>
> Does it work with forward slashes, like this:
>
>   //server/software/file.txt
>
> ?
>
>> [Switching to thread 3636.0x8d4]
>> (gdb) bt full
>> #0  0x77f9193d in ntdll!DbgUiConnectToDbg ()
>>    from /cygdrive/c/WINNT/system32/NTDLL.DLL
>> No symbol table info available.
>> #1  0x7c57fecd in KERNEL32!DebugActiveProcess ()
>>    from /cygdrive/c/WINNT/system32/KERNEL32.DLL
>> No symbol table info available.
>> #2  0x7c57b3bc in lstrcmpiW () from /cygdrive/c/WINNT/system32/KERNEL32.DLL
>> No symbol table info available.
>> #3  0x00000000 in ?? ()
>> No symbol table info available.
>
> This backtrace is not useful.  I think you are in the wrong thread.
>
> Could you please type "info threads" and then switch to each one of
> them (with "thread N", where N is the thread number displayed in the
> 1st column of what "info threads" presents), and find the main thread,
> where the backtrace goes up to the `main' function?  That's the
> backtrace we want to see.
>
> TIA
>






  reply	other threads:[~2008-08-15 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <494D1055.5030508@gnu.org>
2008-08-14 15:00 ` bug#719: Crash opening UNC file john naegle
2008-08-15  7:55   ` Eli Zaretskii
2008-08-15 13:20     ` john naegle [this message]
2008-08-15 17:12       ` Eli Zaretskii
2008-08-15 17:16         ` john naegle
2008-08-16  4:08           ` Stefan Monnier
2008-12-20 15:40   ` bug#719: marked as done (Crash opening UNC file) Emacs bug Tracking System
     [not found] <48A4D102.1010609@f2s.com>
2008-08-15  0:50 ` Processed: another w32 bug Emacs bug Tracking System
2008-08-15  7:48   ` bug#724: " Eli Zaretskii
2008-08-15  9:07     ` Jason Rumney
2008-08-15  9:40       ` Eli Zaretskii
2008-12-20 15:40     ` bug#724: marked as done (Processed: another w32 bug) Emacs bug Tracking System

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb5a18c20808150620u5fc23c24qfe9057048cc1d3bc@mail.gmail.com \
    --to=john.naegle@gmail.com \
    --cc=719@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.