home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!warwick!mrccrc!doc.ic.ac.uk!agate!ames!elroy.jpl.nasa.gov!swrinde!emory!sol.ctr.columbia.edu!eff!iWarp.intel.com|ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!news
- From: hill@norman.VI.RI.CMU.EDU (Robert Hill)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: problem with gdb
- Message-ID: <BxIo9p.142.2@cs.cmu.edu>
- Date: 10 Nov 92 20:15:21 GMT
- Article-I.D.: cs.BxIo9p.142.2
- References: <1992Nov8.023218.11609@Trirex.COM>
- Sender: news@cs.cmu.edu (Usenet News System)
- Organization: School of Computer Science, Carnegie Mellon
- Lines: 18
- Nntp-Posting-Host: alexander.vi.ri.cmu.edu
-
- 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
-