home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!newshost!root
- From: dglattin@trirex.com (Dennis Glatting)
- Subject: Re: problem with gdb
- Message-ID: <1992Nov19.020942.3582@Trirex.COM>
- Sender: root@Trirex.COM (Operator)
- Organization: Trirex Systems Inc.
- References: <BxIo9p.142.2@cs.cmu.edu>
- Date: Thu, 19 Nov 1992 02:09:42 GMT
- Lines: 30
-
- In article <BxIo9p.142.2@cs.cmu.edu> hill@norman.VI.RI.CMU.EDU (Robert
- Hill) writes:
- > Dennis Glatting writes
- > >
- > > A month or two back someone complained that gdb didn't worked when the
- > > *upgraded* to 3.0. What was the resolution on this? I have the same
- > > problem.
- > >
- > > --
- > > Dennis P. Glatting / Sr. Technical Manager / Trirex Systems Inc.
- >
- > I missed the original thread, but I have been having problems with gdb
- > printing the wrong values for variables under 3.0. I'll type something
- > like "print x". I am really sure x has the value of 1, but it says x is
- > 0. At first I thought I was wrong about the value of x, but adding a
- > printf said that x was 1. Very strange.
- >
- > Is there any reported bugs for gdb under 3.0?
- >
- > Rob
-
- I found the answer to my problem. I had a "limit stacksize 10000" in my
- cshrc left over from the pre-collect fix days. I took it out and my
- problem went away.
-
- --
- Dennis P. Glatting / Sr. Technical Manager / Trirex Systems Inc.
- 315 Post Road West / Westport, Connecticut 06880 / (203)221-4600
- dennis_glatting@trirex.com (NeXTmail Ok)
- Member League for Programming Freedom
-