home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!convex!darwin.sura.net!udel!louie!mercury.cis.udel.edu!tirilok
- From: tirilok@mercury.cis.udel.edu (Prem Tirilok)
- Subject: Re: dbx (xde) bugs?
- Message-ID: <1992Jul28.165752.28205@udel.edu>
- Sender: usenet@udel.edu (USENET News Service)
- Nntp-Posting-Host: mercury.cis.udel.edu
- Organization: University of Delaware, Newark
- References: <BLOCK.92Jul20104351@ief.itg.ti.com>
- Distribution: comp
- Date: Tue, 28 Jul 1992 16:57:52 GMT
- Lines: 34
-
- In article <BLOCK.92Jul20104351@ief.itg.ti.com> block@ief.itg.ti.com (Bucky Block) writes:
- >
- >I'm having a problem debugging a large executable using xde/dbx.
- >It brings the program up fine, but when I start single stepping
- >through it, it just hangs. It seems to happen on any subroutine
- >that is doing memory allocation.
-
- >Bucky Block | block@ief.itg.ti.com
-
- I seem to have a similar problem, if not the same. Is there a problem
- with malloc. After a couple of times the following statement is called
- the system gives a "memory fault" and dbx says that it happens at "malloc".
- For your information, repetitive calls to malloc work fine when called
- from "main()" but bomb out when invoked from a subroutine.
-
- The statement that results in the error message is:
-
- token = (char *) malloc (sizeof (char *));
-
- (where token is declared to be "char *token;")
-
- Any ideas and suggestions are welcome. The same program seems to be
- running fine on a SPARCserver (670MP) and SGI (Indigo) workstations,
- of course with a few modifications in other parts of the program.
-
- Thanks
- (Please email suggestions to tirilok@cis.udel.edu)
-
- Prem
- --
- --- O __
- --- <\ ) //)) //)) //__ //\/// \====================
- ---- /> // //\\ //__ // // tirilok@cis.udel.edu
- ==================================================================
-