From:	John Schucker <gwynn AT globaldialog DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Bash and SIGSEGV.
Date:	Sat, 14 Dec 1996 21:35:25 -0600
Organization:	Alpha.net -- Milwaukee, WI
Lines:	46
Message-ID:	<Pine.BSI.3.91.961214213033.1711A-100000@msn.globaldialog.com>
NNTP-Posting-Host:	smtp.globaldialog.com
Mime-Version:	1.0
cc:	ding AT ptd DOT net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I was told to post this trace to the newsgroup, so the person who ported=20
bash could see it.  Accordingly, here is what happens when bash crashes. =
=20
It seems to happen most often when I run qedit for a few times, although=20
it also seems to die simply after being run for a while.  I run from the=20
DOS prompt, after all TSRs are loaded, with the command:
bash -login -i
When it crashes, the following is produced:

Exiting due to signal SIGSEGV=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=
=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=
=C4=C4=C4=C4=C4=C4=D9
General Protection Fault at eip=3D0003dc88
eax=3D00000004 ebx=3D00000000 ecx=3Dfffffffc edx=3D00746162 esi=3D00000003 =
edi=3D00000002
ebp=3D000a6eb0 esp=3D000a6ea8 program=3Dc:/USR/BIN/bash.exe
cs: sel=3D00e7  base=3D100e0000  limit=3D000dffff
ds: sel=3D00ef  base=3D100e0000  limit=3D000dffff
es: sel=3D00ef  base=3D100e0000  limit=3D000dffff
fs: sel=3D00cf  base=3D000203b0  limit=3D0000ffff
gs: sel=3D00ff  base=3D00000000  limit=3Dffffffff
ss: sel=3D00ef  base=3D100e0000  limit=3D000dffff

Call frame traceback EIPs:
  0x0003dc88
  0x000078e0
  0x00006b03
  0x00005dcf
  0x000042b2
  0x0000293a
  0x000211b3
  0x0001b927
  0x00002d75
  0x0004174b
  0x000417a5



I quite like bash, and I was very glad to see that it has been ported.  I=
=20
would like to continue using it.  The simple solution to this would be to=
=20
just do:
trap 'bash -login -i' SIGSEGV
But somehow I think that may be a bad idea, really.  So, if anybody can=20
help ...

- Raw text -