From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1222 invoked by alias); 2 Jul 2007 16:45:01 -0000 Received: (qmail 1211 invoked by uid 22791); 2 Jul 2007 16:45:00 -0000 X-Spam-Check-By: sourceware.org Received: from www.balabit.hu (HELO lists.balabit.hu) (212.92.18.33) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 02 Jul 2007 16:44:58 +0000 Received: from balabit.hu (unknown [10.80.0.254]) by lists.balabit.hu (Postfix) with ESMTP id 9E3E9B555D for ; Mon, 2 Jul 2007 18:44:54 +0200 (CEST) Subject: printing mapped memory regions From: Balazs Scheidler To: gdb@sourceware.org Content-Type: text/plain Date: Mon, 02 Jul 2007 16:45:00 -0000 Message-Id: <1183394699.31266.30.camel@bzorp.balabit> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00013.txt.bz2 Hi, Is it possible to query the list of mapped virtual memory regions of a running process/core file using gdb? I would like something similar to what /proc//maps file provides on Linux, but unluckily that information is not available (grsec zeroes those values so nothing to find there). All I could find was "info shared" but it only prints file-backed regions, I'd like to see mapped stacks for example. "info mem" seems to do something completely different. Is this possible somehow? Thanks in advance. -- Bazsi