[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Is the Cygw32 port ready for testing?
From: |
Ken Brown |
Subject: |
Re: Is the Cygw32 port ready for testing? |
Date: |
Tue, 16 Oct 2012 09:23:28 -0400 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 |
On 10/15/2012 5:36 PM, Daniel Colascione wrote:
On 10/15/2012 2:34 PM, Ken Brown wrote:
On 10/15/2012 5:31 PM, Daniel Colascione wrote:
Emacs builds and starts fine for me even when dbus-daemon is running, with or
without X also running. Running dbus-monitor doesn't report anything happening.
A stack trace from your environment would be helpful.
OK. It will probably be a week or so before I can do this, but there's a slight
chance I'll get to it sooner. Did you definitely build emacs with dbus
support? You need to have libdbus1-devel installed in order for this to happen.
$ ldd emacs.exe
ntdll.dll => /Windows/SysWOW64/ntdll.dll (0x7de70000)
kernel32.dll => /Windows/syswow64/kernel32.dll (0x7dd60000)
KERNELBASE.dll => /Windows/syswow64/KERNELBASE.dll (0x7d850000)
cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
cygdbus-1-3.dll => /usr/bin/cygdbus-1-3.dll (0xc4140000)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cyggif-4.dll => /usr/bin/cyggif-4.dll (0xc3900000)
...
Could you describe your test environment?
I'm running 64-bit Windows 7 with the 2012-09-17 Cygwin snapshot. [I
got similar results on a different machine with the 2012-10-12
snapshot.] The development packages I've installed are shown in the
attached devel.txt file. I'm building emacs with the command
./configure --with-w32 CFLAGS='-g -O0' && make
The Emacs abort dialogue box pops up when the build gets to this point:
gcc -std=gnu99 -Demacs -I. -I/home/kbrown/src/emacs/test-w32/src
-I../lib -I/home/kbrown/src/emacs/test-w32/src/../lib
-I/usr/include/libxml2 -I/usr/include/dbus-1.0
-I/usr/lib/dbus-1.0/include -MMD -MF deps/.d -MP
-I/usr/include/p11-kit-1 -g -O0 -L/usr/lib/noX \
-o temacs pre-crt0.o dispnew.o frame.o scroll.o xdisp.o menu.o
window.o charset.o coding.o category.o ccl.o character.o chartab.o
bidi.o cm.o term.o terminal.o xfaces.o dbusbind.o emacs.o keyboard.o
macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o
minibuf.o fileio.o dired.o cmds.o casetab.o casefiddle.o indent.o
search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o
eval.o floatfns.o fns.o font.o print.o lread.o syntax.o unexcw.o
bytecode.o process.o gnutls.o callproc.o region-cache.o sound.o
atimer.o doprnt.o intervals.o textprop.o composite.o xml.o profiler.o
sheap.o cygw32.o w32fns.o w32menu.o w32reg.o w32font.o w32term.o
w32xfns.o w32select.o w32uniscribe.o fontset.o fringe.o image.o
terminfo.o gmalloc.o lastfile.o vm-limit.o ../lib/libgnu.a
-lkernel32 -luser32 -lgdi32 -lole32 -lcomdlg32 -lusp10 -lcomctl32
-lwinspool -ltiff -ljpeg -lpng -lz -lm -lgif -lXpm -ldbus-1
-lpthread -lrt -lxml2 -lz -liconv -lm -lncurses
-L/usr/bin -lgnutls -lnettle -lhogweed -lgmp -ltasn1 -lp11-kit -lz
-lpthread
test "no" = "yes" || \
test "X" = X || -r temacs.exe
cd ../lisp; make -w update-subdirs
make[2]: Entering directory `/home/kbrown/src/emacs/test-w32/lisp'
cd /home/kbrown/src/emacs/test-w32/lisp; subdirs=`find . -type d
-print`; for file in $subdirs; do case $file in */.* | */.*/* | */=* |
*/cedet* ) ;; *) wins="$wins $file" ;; esac; done; \
for file in $wins; do \
/home/kbrown/src/emacs/test-w32/build-aux/update-subdirs $file; \
done;
make[2]: Leaving directory `/home/kbrown/src/emacs/test-w32/lisp'
if test "no" = "yes"; then \
rm -f bootstrap-emacs.exe; \
ln temacs.exe bootstrap-emacs.exe; \
else \
`/bin/pwd`/temacs --batch --load loadup bootstrap || exit 1; \
test "X" = X || -zex emacs.exe; \
mv -f emacs.exe bootstrap-emacs.exe; \
fi
At this point I attached gdb. The session didn't provide any
information that I can see, but I'm attaching a log (gdb.txt).
My build was based on the trunk as of bzr revision 110552.
FWIW, here's a stack trace from an earlier build attempt in which I
didn't attach gdb and just let emacs abort:
0028A714 76A61194 (000001A8, 0000EA60, 00000000, 0028A848)
0028A728 76A61148 (000001A8, 0000EA60, 000000A4, 0028A824)
0028A848 610DC649 (03FA135C, 00000000, 03D4E5E8, 03FA13C8)
0028A938 610D9893 (00000000, 0000000A, 03D490B8, 03D490B8)
0028A998 610D9D6E (00000008, 007B53C0, 6B00076C, 00000006)
0028AA48 610D9EC0 (00001FF8, 00000006, 03D219D8, 0028AA7C)
0028AA68 610D9EEC (00000006, 00000006, FFFFFFFF, 0028AA98)
0028AA98 610DA1B3 (00000000, 00752438, 00752423, 00012034)
0028AAB8 005603C7 (0028AC24, 0028AAF0, 0028AB28, 00498BB4)
0028AAC8 004F070B (0079E4EC, 007412BE, 0079E4EC, 0079B3B0)
0028AB28 00498BB4 (00800C92, 0080022A, 007B7432, 0028AC34)
0028AC58 0049A75A (00000005, 0028AC80, 007A2F00, 611A1E96)
0028ACF8 6100763A (00000000, 0028CD78, 61006C50, 00000000)
gdb.txt
Description: Text document
devel.txt
Description: Text document
- Re: Is the Cygw32 port ready for testing?, (continued)
- Re: Is the Cygw32 port ready for testing?, Daniel Colascione, 2012/10/14
- Re: Is the Cygw32 port ready for testing?, Daniel Colascione, 2012/10/14
- Re: Is the Cygw32 port ready for testing?, Andreas Schwab, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Ken Brown, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Eli Zaretskii, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Ken Brown, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Daniel Colascione, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Daniel Colascione, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Ken Brown, 2012/10/15
- Re: Is the Cygw32 port ready for testing?, Daniel Colascione, 2012/10/15
- Re: Is the Cygw32 port ready for testing?,
Ken Brown <=
- Re: Is the Cygw32 port ready for testing?, Eli Zaretskii, 2012/10/16
- Re: Is the Cygw32 port ready for testing?, Stephen J. Turnbull, 2012/10/17
- Re: Is the Cygw32 port ready for testing?, Eli Zaretskii, 2012/10/17
- Re: Is the Cygw32 port ready for testing?, Stephen J. Turnbull, 2012/10/17
- Re: Is the Cygw32 port ready for testing?, Nix, 2012/10/17
- Re: Is the Cygw32 port ready for testing?, Ken Brown, 2012/10/18
- Re: Is the Cygw32 port ready for testing?, Daniel Colascione, 2012/10/18
- Re: Is the Cygw32 port ready for testing?, Ken Brown, 2012/10/18
- Re: Is the Cygw32 port ready for testing?, Eli Zaretskii, 2012/10/18
- Re: Is the Cygw32 port ready for testing?, Stefan Monnier, 2012/10/18