public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Burton Samograd <kruhft@hotmail.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] random gdb "debugger segfaults"
Date: Sat, 15 Nov 2003 13:11:30 -0800	[thread overview]
Message-ID: <87fzgp5ocd.fsf@kruhft.vc.shawcable.net> (raw)

Hi,

I'm not sure if this is a gentoo problem, but I figured I would get a
better response through this list than gentoo-user.

I'm working on a new C program and I'm getting a number of debugger
segfaults when running gdb.  I've never had such a vital program as
gdb crash on me before, so this has gotten me a bit worried about
possible library mismatches or problems with newer versions
gcc/binutils/gdb working together.

I'm working with shared libraries in this application for the first
time, and I thought that gdb might be a bit flakey with this type of
dynamic symbol allocation.  Anybody have experience with this?

I don't know if there's a current solution, but I thought that I
wouldn't be alone is seeing these problems and that others might have
already found the source (and solution). Currently I'm running:

gdb 6.0
gcc 3.3.2-r2
binutils 2.14.90.0.7

Note that gdb does work, but crashes rather randomly (as in, I can't
see a definite pattern that I could nail down to an actual bug)
requiring a restart, which is a bit irritating but not life
threatening.

-- 
burton samograd
http://kruhftwerk.dyndns.org


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-11-15 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15 21:11 Burton Samograd [this message]
2003-11-16  9:47 ` [gentoo-dev] random gdb "debugger segfaults" Paul de Vrieze
2003-11-17  0:29   ` [gentoo-dev] " Burton Samograd

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=87fzgp5ocd.fsf@kruhft.vc.shawcable.net \
    --to=kruhft@hotmail.com \
    --cc=gentoo-dev@gentoo.org \
    /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