Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Maciej Kalisiak <mac@cs.toronto.edu>
To: gdb@sourceware.cygnus.com
Subject: problem with "info shared", running programs
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <20010301100153.B1123@khazad-dum> (raw)

I've been experiencing a problem with gdb 5.0 on a linux 2.2 system (Debian,
using the most recent .deb from "unstable").  This is with libc6 2.2.1. As far
as the libraries linked, here's "ldd =gdb":
        libncurses.so.5 => /lib/libncurses.so.5 (0x40022000)
        libm.so.6 => /lib/libm.so.6 (0x40060000)
        libdl.so.2 => /lib/libdl.so.2 (0x4007e000)
        libc.so.6 => /lib/libc.so.6 (0x40082000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

For some time now, whenever I run a program, right at the beginning I get
interrupted twice with
  Cannot access memory at address 0x40016de0
and have to hit continue.  This was a pain, but workable.  I used to not get
this problem before when I ran under 'icewm', but I used to get it under 'KDE
kwm'.  Now I get it under 'icewm'.

What's more interesting, I found out today about "info {shared|file}", and
decided to try it.  "info file" works great, but "info shared" again
complains:
  Cannot access memory at address 0x40016de0

This makes me think that this is somehow related to the shared objects that
are being used...  I did some upgrades just before the first time this started
complaining, so perhaps that's the problem.  Any thoughts?

-- 
Maciej Kalisiak		mac@dgp.toronto.edu	www.dgp.toronto.edu/~mac


                 reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010301100153.B1123@khazad-dum \
    --to=mac@cs.toronto.edu \
    --cc=gdb@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox