Mail Archives: djgpp-workers/1996/05/06/01:18:53
A user complained that he cannot debug with gdb under Windows 3.11. The
report looked just like what was happening in v1.x, but the guy insisted
it happens to him in v2, no matter what the memory settings are, so I
tried it too. Guess what? it bombs for me too, at least on one of the
machines I work on (fsdb works though). I could almost swear the bug
didn't exist in the past, but I seldom develop under Windows, so can't
say for sure nor guess what configuration changes could cause this.
I will test this on several other systems, but if anybody can debug with
gdb under Windows, please say so. The basic problem is that any program
(either toy or not, I tested several short ones and Emacs) will get
SIGSEGV (or is it gdb that gets it?) if you set a breakpoint and run it.
---------- Forwarded message ----------
Date: Fri, 3 May 1996 13:33:14 +0200 (MET DST)
From: Jan Hansen <jaha AT daimi DOT aau DOT dk>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject: Re: GDB breakpoint problem
>
>
> On 29 Apr 1996, Jan Hansen wrote:
>
> > When the execution reaches the breakpoint, i get this message:
> > exception SIGSEGV, segmentation fault
> > And then i can't continue (using n or s)
> >
> > i'm using a 120MHz Pentium with 8Mb ram.
> > The debugger is running in a Windows 3.11 dos window.
>
> Did you set the maximum EMS and XMS amounts to -1 on the `dosprmpt.pif'
> file? (The FAQ list tells you to do so in sections 3.8 and 15.8.) If
> you did and it won't help, please invoke go32-v2 without arguments in the
> DOS box and post everything it prints.
>
output from go32-v2
go32/v2 version 2.0 built Jan 23 1996 22:03:02
Usage: go32 coff-image [args]
Rename this to go32.exe only if you need a go32 that can run v2 binaries as
well as v1 binaries (old makefiles). Put ahead of the old go32 in your PATH.
DPMI memory available: 1952 Kb
DPMI swap space available: 14552 Kb
compiling with: gcc -g -otst tst.c (version 2.7.2)
and debugging with: gdb tst
GDB is free software and you are welcome to 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.
GDB 4.12 (go32), Copyright 1994 Free Software Foundation, Inc...
(gdb) l
1 #include<stdio.h>
2 main()
3 {
4 printf("a\n");
5 printf("b\n");
6 printf("c\n");
7 printf("d\n");
8 };
(gdb) b 5
Breakpoint 1 at 0x155d: file tst.c, line 5.
(gdb) r
Starting program: c:/djgpp/work/tst/tst
Program received signal SIGSEGV, Segmentation fault.
0x1564 in main () at tst.c:5
5 printf("b\n");
(gdb) n
Program received signal SIGSEGV, Segmentation fault.
0x1564 in main () at tst.c:5
5 printf("b\n");
(gdb) s
Program received signal SIGSEGV, Segmentation fault.
0x1564 in main () at tst.c:5
5 printf("b\n");
(gdb) quit
go32_kill_inferior called
As you can see, the problem occurs at the breakpoint.
It does not matter what program i debug, it simply does not work.
Jan Hansen.
- Raw text -