Dear managers,
A few weeks ago I made an upgrade from OSF 2.0 to 3.2C. Seems like
everything went fine till I tried to run gdb. When I try to run gdb on a
file which is generated on a digital 3.2C version I can't use the
back-trace option anymore.
I got a recurring stack in the __start () part.
(gdb) run
Starting program: /usr/users/colle/ircdir/a.out
Breakpoint 1, main () at ybot.c:82
82 connectIRC();
(gdb) ba
#0 main () at ybot.c:82
#1 0x120001770 in __start ()
#2 0x120001770 in __start ()
#3 0x120001770 in __start ()
#4 0x120001770 in __start ()
#5 0x120001770 in __start ()
#6 0x120001770 in __start ()
When i compile the same file on a machine running osf v2.0 I get this result:
(gdb) run
Starting program: /usr/users/colle/ircdir/a.out
Breakpoint 1, main () at ybot.c:82
82 connectIRC();
(gdb) ba
#0 main () at ybot.c:82
I did a file on the executables which were generated with both version of
OSF, and there seems to be a difference:
colle_at_krtkg1> file test.c.osf2.0
a.out: COFF format alpha dynamically linked, demand paged executable or
object module not stripped - version 3.11-4
colle_at_krtkg1> file test.c.du3.2c
a.out: COFF format alpha dynamically linked, demand paged executable or
object module not stripped - version 3.11-8
What makes gdb (which I recompiled on a digital unix 3.2c machine) fail
on the backtrace and are there any solutions to this problem?
I'm planning to upgrade our last machine to digital unix 3.2c, but before
I want to be sure that I will still be able to use gdb.
Any help is appreciated.
Thanks,
Christophe Colle
| \ =============================================================
| \ Colle Christophe Phone: +32-(0)9-2403955
+---- mail: colle_at_krtkg1.rug.ac.be
http://krtkg1.rug.ac.be/~colle
|
----------+ When I'm not in Ghent, Then I'm probably Sailing
\________| ======= Radiotherapy Department, Ghent =============
Received on Thu Dec 28 1995 - 16:56:05 NZDT