In further release please consider to catch X11/dejavu-fonts in dependency list
of git-gui & gitk.
XP/SP3
$ uname -a
CYGWIN_NT-5.1 VladiLaptopWXP 2.4.1(0.293/5/3) 2016-01-24 11:24 i686 Cygwin
$ cygcheck -s|grep -i git
git 2.7.0-1OK
git-gui
On 29.01.2016 03:04, Matt Seitz wrote:
> When I try to run "git gui" I get the following error:
>
> Matt@hp /cygdrive/c/Users/Matt
> $ git gui
> error: git-gui died of signal 11
>
> Log files attached.
It looks like you called `git gui` from your home direc
When I try to run "git gui" I get the following error:
Matt@hp /cygdrive/c/Users/Matt
$ git gui
error: git-gui died of signal 11
Log files attached.
Sincerely,
Matt Seitz
cygcheck.out
Description: cygcheck.out
wish8.5.exe.stackdump
Description: wish8.5.exe.stackdump
--
Probl
- native DPI x 96 y 96
[104131.312] Could not load crashreporter dll
[104131.343] Fatal signal received in thread 0x2038 [0x1164]
[104131.343] (EE) Segmentation fault at address 0x1
[104131.484] (EE) /usr/bin/xorg-backtrace failed with returncode 0
[104131.484] (EE) Fatal server error:
backtrace failed with returncode 0
[104131.484] (EE) Fatal server error:
[104131.484] (EE) Caught signal 11 (Segmentation fault). Server aborting
[104131.484] (EE) Server terminated with error (1). Closing log file.
<<<
--
Problem reports: http://cygwin.com/problems.html
FAQ:
27;axcient'...
remote: Counting objects: 169130, done.
remote: Compressing objects: 100% (74011/74011), done.
fatal: write error: Broken pipe169130), 282.85 MiB | 19.03 MiB/s
error: index-pack died of signal 11
fatal: index-pack failed
Administrator@MATER2K8SHPT /cygdrive/d/cygwin
$
--
Problem repo
On 23 May 2006 23:22, Michael Williamson wrote:
> The linker crashes when I try to compile the
> camera software LinuxDevKit.tar for SBIG cameras:
>
> g++ -I . -L . -Wall -o testapp testmain.cpp
> csbigcam.cpp
> -csbingimg.cpp -lsbigudrv
> collect2: ld term
The linker crashes when I try to compile the
camera software LinuxDevKit.tar for SBIG cameras:
g++ -I . -L . -Wall -o testapp testmain.cpp
csbigcam.cpp
-csbingimg.cpp -lsbigudrv
collect2: ld terminated with signal 11 [Segmentation
fault], core dumped
Why does this happened
On Sun, Sep 14, 2003 at 12:21:27PM +0100, [EMAIL PROTECTED] wrote:
>My reluctance to attach cygcheck output stems from not knowing what's best
>to send. So here (two attachments) is the output from cygcheck -c (I
>understand some or all "Incomplete"s not to matter) and from cygcheck -srv.
>Thanks a
hris, Harold and Jan for
picking this up. You have helped greatly, as follows:
Start -> Run -> start XWin -multiwindow
Start -> Run -> run rxvt -display localhost:0.0 -e bash --login -i
xdvi a4.dvi
Signal 11
xdvi.bin a4.dvi
** successful presentation to screen of a4.dvi **
My
> After some recent large updates including XFree* and tetex* and texmf* I am
> still getting a "Signal 11" error msg after a request to xdvi a .dvi file.
> This is after starting XWin -multiwindow and when running rxvt -display.
> Anybody else getting this or similar, or
ter have a legitimate question.
Hmm. AFAICT, this discussion does belong in both groups until we narrow
down what is causing the crash.
You say you are getting a "Signal 11" error message, but I don't see a
reference to which program is actually crashing.
Previous email mentions tha
own what is causing the crash.
>You say you are getting a "Signal 11" error message, but I don't see a
>reference to which program is actually crashing.
Previous email mentions that the program in question is xdvi. It even
received confirmation, right here in cygwin-xfree.
On Sat, Sep 13, 2003 at 06:03:07PM +0100, [EMAIL PROTECTED] wrote:
>After some recent large updates including XFree* and tetex* and texmf* I am
>still getting a "Signal 11" error msg after a request to xdvi a .dvi file.
>This is after starting XWin -multiwindow and when ru
After some recent large updates including XFree* and tetex* and texmf* I am
still getting a "Signal 11" error msg after a request to xdvi a .dvi file.
This is after starting XWin -multiwindow and when running rxvt -display.
Anybody else getting this or similar, or recognise the symptom?
ronment dump, I'm still using gcc3). So, I insist: there is a bug in
>1.3.20-1 (reproducable by building xemacs-21.4.12) that has not been in
>1.3.18.
I have loosly followed this thread... I have had a similar problem after
updating
to 1.3.20. When compiling I got random signal 11 cras
On Fri, Mar 07, 2003 at 08:56:30AM +0100, Michael Lipp wrote:
>I think you are missing an important point: I can build xemacs
>successfully when I use the older (1.3.18) cygwin1.ddl! That's the only
>thing I have changed about the environment (as you can see in the
>environment dump, I'm still u
e this helps.
I downloaded the XEmacs 2.4.12 sources from www.xemacs.org, unpacked and
configured with "./configure --with-msw=yes --with-x11=no
--prefix=/usr/local/xemacs".
Running `make? goes very far, but finally it fails with "signal 11". Not
during C-compilation, but when x
packed and
> configured with "./configure --with-msw=yes --with-x11=no
> --prefix=/usr/local/xemacs".
>
> Running `make? goes very far, but finally it fails with "signal 11". Not
> during C-compilation, but when xemacs tries to do something with the
> lisp
w=yes --with-x11=no
--prefix=/usr/local/xemacs".
Running `make? goes very far, but finally it fails with "signal 11". Not
during C-compilation, but when xemacs tries to do something with the
lisp code, so this seems to be a reproducable case of my initial problem.
I then downgra
[This followup was posted to gmane.comp.gcc.devel and a copy
was sent to the cited author.]
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] says...
> It's not a GCC problem.
>
> Cygwin 1.3.19 added in support for vasprintf (previously GCC
> would use the version included in libiberty).
>
DCYGWIN_CROSS_DIR=\"/usr/local/i686-pc-cygwin\" -I. -I. -I../../gcc/g
> cc -
> I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include \
> ../../gcc/gcc/gengtype-yacc.c -o gengtype-yacc.o
> gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
>
I know. 20030502 works fine for now.
No more signal 11 (error 123 I think was the other one)
Going further, you can see where some names are used, but not defined.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Kelley Cook
Sent: Thursday, February 06
Haven't found the problem, but I've narrowed it down some, so this is mainly
to see if anybody's memory gets jogged:
I'm gdb'ing "gengtype.exe", the executable that's "Signal 11"ing and killing
the compile of GCC cvs HEAD on cygwin1.dll versions
SOrry for crossposting.
Gcc 3.3=branch give me a Signal 11.
here's the error
gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prot
otypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_
FILE
-o gengtype.exe \
gengtype.o gengtype-
I'm getting "Signal 11"s (whatever that is) when doing a build of gcc from
cvs (cross):
"
[...]
make[1]: Entering directory `/home/grvs/build-newgcc/gcc'
./gengtype
Signal 11
make[1]: *** [s-gtype] Error 139
[...]
"
gengtype is an exe, it generated a stack dump (att
At 03:57 AM 12/19/2001, Neil Bird wrote:
> Nobody seems to have had any comment WRT my continued, random 'signal 11' errors
>trying to configure and/or make (even in a make clean!).
>
> If I run purely off a C:\-installed cygwin, I suffer no problems at all - I seem
I had random signal 11 problems. In desparation, I completely cleansed my
computer of all things cygwin, and reinstalled. I haven't had one since.
YMMV, but if you decide to do this, save any personal files, remove the
cygwin directory, and the registry keys, then reinstall.
Nobody seems to have had any comment WRT my continued, random
'signal 11' errors trying to configure and/or make (even in a
make clean!).
If I run purely off a C:\-installed cygwin, I suffer no
problems at all - I seem to have compiled up gcc fine.
So - why would runn
onfigure' in a clean directory, I
get random 'Signal 11' (seg. viol.?) messages come up, mostly in
the checking phase, but occasionally also in the
Makefile-generation phase at the end.
They don't appear to happen in the same place each time.
Typically, though, a '
30 matches
Mail list logo
