Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Warno <keith.warno@valaran.com>
To: gdb list <gdb@sourceware.cygnus.com>
Subject: 1) SIGTRAP issue :/ 2) libbfd
Date: Mon, 25 Jun 2001 09:21:00 -0000	[thread overview]
Message-ID: <3B376519.60D5AE3F@valaran.com> (raw)

1) I recently upgraded glibc on one linux box to 2.2.2.  I built it from
source tarballs and now, for whatever reason, I cannot debug any
programs with gdb.  I wind up with something like the following:

(gdb) run
Starting program: /home/kw/a.out 

Program received signal SIGTRAP, Trace/breakpoint trap.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x40001fa0 in ?? ()
(gdb)

Hrmm ok so maybe I left out a configuration option or two with the glibc
build?  If so, any thoughts?  I haven't any idea.
gcc here is ver. 2.95.3 & the kernel is 2.2.19.

2) libbfd is distributed with gdb and binutils.  I would like to rebuild
gcc, gdb, and binutils and I know that the three of them can be built
together.  Question is: will the differing versions of libbfd provided
with gdb and binutils potentially cause any issues, and if so how could
such issues be avoided?

Regards,
kw

--                           
| Keith Warno                       cell: +1 609-209-5800
| http://www.valaran.com/           work: +1 609-716-7200 x243
| Valaran Corporation Penguin Guy   SMS : kw-mobile@valaran.com
+--------------------------------------------------------------//


             reply	other threads:[~2001-06-25  9:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25  9:21 Keith Warno [this message]
2001-06-25 10:17 ` Keith Warno
2001-06-25  9:41 Michael Elizabeth Chastain

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=3B376519.60D5AE3F@valaran.com \
    --to=keith.warno@valaran.com \
    --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