This is the mail archive of the mailing list for the Cygwin project. See the Cygwin home page for more information.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

[ GDB and newest snapshots]

----- Forwarded message from -----

Date: Fri, 16 Apr 1999 22:31:40 -0400
X-Sender: "" <> (Unverified)
X-Mailer: Mozilla 4.5 [en]C-gatewaynet  (Win98; U)
X-Accept-Language: en
To: Chris Faylor <>
Subject: GDB and newest snapshots

	It seems I am banned again from the mail-list.  Same problem as
before.  Could you forward the to the developers list.

John Fortin...

> all,
> Looking at this a bir more closely, it seems that GDB itself is OK.  The
> failure is in loading the program to be debugged when it is a 'cygwin'
> linked program. Probably in the initialization before main() is
> executed.  The program being debugged fails in
> _size_of_stack_reserve().  The memory location of the executed statement
> is 0xbffa0eb2 which is in the system dll area for win98
> (0x80000000-0xBFFFFFFF)
> It says it cannot access memory at 0x2000000 ( and hence the SIGSEGV).
> This is in the program's private  address space (0x00400000 -
> 0x7FFFFFFF) So it should be able to read this unless it has been locked
> or set unreadable somehow.
> Unfortunately, I haven't a clue where to begin debugging this.  It looks
> like the function  may be in kernel32.dll or advapi32.dll, but I can't
> get a trace as to how it was called.  I don't pretend to understand how
> gdb starts a program executing ( some type of fork() ? )
> When I looked in the Changelog, I did see that there were changes in
> varios type of shared memory on Mar. 31 and it is after this that the
> cygwin1.dll and gdb don't work well together.
> As I mentioned before, programs compiled with -mno-cygwin work fine.
> If any other info is needed, please let me know.
> John Fortin,
> wrote:
> > 4
> > All,
> >
> > I compiled GDB 4.17.87 with the April 8th cygwin-src snapshot.  Compiled
> > fine.
> >
> > However, whenever i try to run a program, it gets a SIGSEGV in
> > _size_of_stack_reserve().
> >
> > When I used a cygwin1.dll from march 30 and earlier ( from the snapshot
> > site ) it works fine.
> >
> > The latest 2 snapshot dlls will not even run bash.exe.
> >
> > Thanks,
> > John Fortin

----- End forwarded message -----