From: Albert Chin <gdb@mlists.thewrittenword.com>
To: gdb@sourceware.org
Subject: SEGV running gdb-6.7 on Tru64 UNIX 5.1
Date: Wed, 17 Oct 2007 23:38:00 -0000 [thread overview]
Message-ID: <20071017233802.GA74638@mail1.thewrittenword.com> (raw)
Anyone running 6.7 successfully on Tru64 UNIX 5.1? gdb-6.6 Worked ok.
% cat a.c
#include <stdio.h>
int
main (void) {
puts ("a");
}
% cc -g a.c
% gdb-6.6 a.out
gdb> list
...
% gdb-6.7 a.out
gdb> list
Memory fault - core dumped
% ladebug gdb-6.7 a.out
ladebug> where
>0 0x120125920 in symbol_found(funfirstline=1, canonical=0x0, copy=0x1401778d0="main", sym=0x14014d7c0, file_symtab=0x0, sym_symtab=0x0) "linespec.c":1786
#1 0x120125744 in decode_variable(copy=0x1401778d0="main", funfirstline=1, canonical=0x0, file_symtab=0x0, not_found_ptr=0x0) "linespec.c":1737
#2 0x120123a80 in decode_line_1(argptr=0x11fffb7a8, funfirstline=1, default_symtab=0x0, default_line=0, canonical=0x0, not_found_ptr=0x0) "linespec.c":859
#3 0x1200beb94 in decode_line_spec(string=0x1401260a4="", funfirstline=1) "symtab.c":4095
#4 0x120081a64 in select_source_symtab(s=0x0) "source.c":244
#5 0x1200818d4 in set_default_source_symtab_and_line() "source.c":180
#6 0x12008a008 in list_command(arg=0x0, from_tty=1) ".././gdb/cli/cli-cmds.c":735
#7 0x1200a1cd0 in do_cfunc(c=0x14013ee00, args=0x0, from_tty=1) ".././gdb/cli/cli-decode.c":60
#8 0x1200a5118 in cmd_func(cmd=0x14013ee00, args=0x0, from_tty=1) ".././gdb/cli/cli-decode.c":1663
#9 0x120085e00 in execute_command(p=0x1400e0484="", from_tty=1) "top.c":449
#10 0x1200a0560 in command_handler(command=0x1400e0480="list") "event-top.c":518
#11 0x1200a10dc in command_line_handler(rl=0x140177820="") "event-top.c":804
#12 0x3ffbffefe20 in rl_callback_read_char(...) in /opt/fsw/readline52/lib/libreadline.so.7
Any ideas?
--
albert chin (china@thewrittenword.com)
next reply other threads:[~2007-10-17 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 23:38 Albert Chin [this message]
2007-10-18 3:20 ` Joel Brobecker
2007-10-18 16:52 ` Albert Chin
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=20071017233802.GA74638@mail1.thewrittenword.com \
--to=gdb@mlists.thewrittenword.com \
--cc=gdb@sourceware.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