From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4617d1fd94f5b239,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-01-28 20:04:47 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!colt.net!easynet-quince!easynet.net!news-peer.gradwell.net!not-for-mail
Newsgroups: comp.lang.ada
From: porton@ex-code.com (Victor Porton)
Date: Wed, 29 Jan 2003 09:02:26 +0500
Organization: Extreme Code Software (http://ex-code.com)
Subject: Gnat: gmem does not work
Mime-Version: 1.0
X-Newsreader: knews 1.0b.1
Content-Type: text/plain; charset=us-ascii
X-URL: http://www.ex-code.com/
Message-ID: <3e3752dd$0$345$bed64819@news.gradwell.net>
NNTP-Posting-Date: 29 Jan 2003 04:04:45 GMT
NNTP-Posting-Host: 195.149.39.13
X-Trace: 1043813085 news.gradwell.net 345 mail2news/195.149.39.13
X-Complaints-To: news-abuse@gradwell.net
Xref: archiver1.google.com comp.lang.ada:33532
Date: 2003-01-29T04:04:45+00:00
List-Id: <comp.lang.ada>

Gnat 3.14p, GNU gdb 2002-04-01-cvs (Linux/i386)

Despite of I link with -lgmem the file gmem.out is not produced. Any 
ideas? (The program aborts with Storage_Error.)

Yes, the linker options are correct and -lgmem is really passed to the 
linker. (I checked using -v flag and seeing the linker command line in 
full.)

Yes, the current working directory is existing and writable.

Running in GDB mode also does not work:

$ gnatmem parser_test
gdb: Symbol `emacs_ctlx_keymap' has different size in shared object, consider re-linking

### incorrect user program  termination detected.
    following data may not be meaningful

Global information
------------------
   Total number of allocations        :   0
   Total number of deallocations      :   0
   Final Water Mark (non freed mem)   :   0 Bytes
   High Water Mark                    :   0 Bytes