This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: gdb is coring on me, "bus error"
- From: "Grant Schoep" <gschoep at digitalglobe dot com>
- To: <gdb at sources dot redhat dot com>
- Date: Fri, 12 Mar 2004 18:06:15 -0700
- Subject: RE: gdb is coring on me, "bus error"
update, well I figured out what is causing the problem. It is a specific
.so file I am linking in to the app.
If I remove the code that needs that library, and remove the " -Bdynamic
-lbadlib " from my link line... all works good.
Any ideas as to why this may be? ... is there a way I can tell the
debugger to ignore this library? The calls in this library I don't want
to debug anyways. Just my app.
-grant
-----Original Message-----
From: Grant Schoep
Sent: Friday, March 12, 2004 4:57 PM
To: 'gdb@sources.redhat.com'
Subject: gdb is coring on me, "bus error"
My Setup...
-Solaris 9
-gdb version 6.0(was prebuilt version from http://www.sunfreeware.com/)
The "gdb -v" output.
GNU gdb 6.0
...snip...
This GDB was configured as "sparc-sun-solaris2.9".
Ok, gdb seems to debug a number of apps fine. I have one app that I am
just starting to develop and whenever I run the apps under gdb, gdb
itself core dumps with a bus error...
This particular app is rather funky with threads and socket use. Is
there any known issues?
Oh... I also believe that some of the libaries that I need to link to
were built by the Sun Pro compier. Are these "known problems?"
I've built my own version of gdb, so I could debug it a bit more(still
cores in same way). Stack trace from it is as follows.
(gdb) where
#0 0xff0428e4 in t_splay () from /usr/lib/libc.so.1
#1 0xff042750 in t_delete () from /usr/lib/libc.so.1
#2 0xff0423a0 in realfree () from /usr/lib/libc.so.1
#3 0xff042b8c in _free_unlocked () from /usr/lib/libc.so.1
Any ideas on what I could look into or what I am doing wrong?
-grant