From: Fernando Nasser <fnasser@redhat.com>
To: Barry Branham <bbranham@networkusa.net>
Cc: insight@sourceware.cygnus.com
Subject: Re: insight crash
Date: Sat, 06 Jan 2001 15:40:00 -0000 [thread overview]
Message-ID: <3A57ACA5.C336387E@redhat.com> (raw)
In-Reply-To: <3A57A8F3.F0B8FB49@networkusa.net>
The stack trace you posted (although incomplete) seems to indicate
that there was a problem reading the symbols of a C++ program.
Why don't you try calling GDB with the "-nw" parameter and see if it
crashes or not? This way we can confirm where the problem lies.
Fernando
P.S.: Was this C++ program generated with g++? Which version?
Barry Branham wrote:
>
> Hi,
>
> Insight crashes when I run it on on RedHat 7.0. I was using it
> previously on RH 6.2 and it ran fine. I recently upgraded to RH7.0 and
> installed insight+dejagnu-20001213. It config'd ok, make'd with minor
> warnings and installed ok.
>
> When I run with an executable as argument, it a long time passes and
> then it seg faults.
> Without an argument it displays an empty source window - no menu bar etc
> but doesn't crash.
>
> Today I got similiar results with insight+dejagnu-20010106.
> When it crashes, 'gdb /usr/local/bin/gdb core' (regular gdb) gives the
> following:
>
> [bhb@vger bhb]$ gdb /usr/local/bin/gdb core
> GNU gdb 5.0
> Copyright 2000 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "i386-redhat-linux"...
> Core was generated by `/usr/local/bin/gdb /usr/local/bin/Dash'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/lib/libncurses.so.5...done.
> Loaded symbols for /usr/lib/libncurses.so.5
> Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
> Loaded symbols for /usr/X11R6/lib/libX11.so.6
> Reading symbols from /lib/libdl.so.2...done.
> Loaded symbols for /lib/libdl.so.2
> Reading symbols from /lib/libm.so.6...done.
> Loaded symbols for /lib/libm.so.6
> Reading symbols from /lib/libc.so.6...done.
> Loaded symbols for /lib/libc.so.6
> Reading symbols from /lib/ld-linux.so.2...done.
> Loaded symbols for /lib/ld-linux.so.2
> Reading symbols from /lib/libthread_db.so.1...done.
> Loaded symbols for /lib/libthread_db.so.1
> #0 0x401cb245 in chunk_alloc (ar_ptr=0x0, nb=0) at malloc.c:2736
> 2736 malloc.c: No such file or directory.
> (gdb)
>
> backtrace gives this:
>
> (gdb) bt
> #0 0x401cb245 in chunk_alloc (ar_ptr=0x0, nb=0) at malloc.c:2736
> #1 0x401cb08e in __libc_malloc (bytes=32) at malloc.c:2704
> #2 0x80d853a in xmmalloc (md=0x0, size=32) at utils.c:1024
> #3 0x80d85a8 in xmalloc (size=32) at utils.c:1059
> #4 0x8185274 in string_need (s=0xbf800290, n=16) at cplus-dem.c:4721
> #5 0x81853c5 in string_appendn (p=0xbf800290,
> s=0x8569814 "mainWindowWidget__C14VkSimpleWindow", n=16) at
> cplus-dem.c:4808
> #6 0x8184dc2 in demangle_function_name (work=0xbf8002d0,
> mangled=0xbf8002c4,
> declp=0xbf800290, scan=0x8569824 "__C14VkSimpleWindow") at
> cplus-dem.c:4558
> #7 0x8182963 in iterate_demangle_function (work=0xbf8002d0,
> mangled=0xbf8002c4,
> declp=0xbf800290, scan=0x8569824 "__C14VkSimpleWindow") at
> cplus-dem.c:2569
> #8 0x8182e5f in demangle_prefix (work=0xbf8002d0, mangled=0xbf8002c4,
> declp=0xbf800290) at cplus-dem.c:2818
> #9 0x8180c80 in internal_cplus_demangle (work=0xbf8002d0,
> mangled=0x8569814 "mainWindowWidget__C14VkSimpleWindow") at
> cplus-dem.c:1108
> #10 0x8180971 in cplus_demangle (
> mangled=0x8569814 "mainWindowWidget__C14VkSimpleWindow", options=3)
> at cplus-dem.c:928
> #11 0x80960d8 in lookup_symbol (
> name=0x8569814 "mainWindowWidget__C14VkSimpleWindow",
> block=0x86fc7c8,
> namespace=VAR_NAMESPACE, is_a_field_of_this=0x0, symtab=0x0) at
> symtab.c:587
> #12 0x8096100 in lookup_symbol (
> name=0x8569814 "mainWindowWidget__C14VkSimpleWindow",
> block=0x86fc7c8,
> namespace=VAR_NAMESPACE, is_a_field_of_this=0x0, symtab=0x0) at
> symtab.c:595
> #13 0x8096100 in lookup_symbol (
> name=0x8569814 "mainWindowWidget__C14VkSimpleWindow",
> block=0x86fc7c8,
> ---Type <return> to continue, or q <return> to quit---q
>
> subsequent frames repeat...
>
> So it looks like we're running out of memory. Running top during this
> shows size getting up to 25Mb before the segfault.
>
> Any help much appreciated.
> Barry Branham
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-01-06 15:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 15:19 Barry Branham
2001-01-06 15:40 ` Fernando Nasser [this message]
2001-01-06 19:09 ` Barry Branham
2001-01-07 7:17 ` Fernando Nasser
2001-01-07 8:51 ` Barry Branham
2001-01-07 10:07 ` Fernando Nasser
2001-01-07 13:44 ` Barry Branham
2001-01-07 15:46 ` Fernando Nasser
2001-01-07 19:03 ` Barry Branham
2001-01-08 4:57 ` Fernando Nasser
2001-01-08 5:37 ` Barry Branham
2001-01-08 7:10 ` Fernando Nasser
2001-01-15 7:08 ` Barry Branham
2001-01-15 7:30 ` Fernando Nasser
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 7:49 Insight crash Tom Tromey
2001-12-04 20:49 ` Tom Tromey
2001-05-11 16:48 Tom Tromey
2001-05-11 17:10 ` Fernando Nasser
2001-05-11 18:48 ` Tom Tromey
2000-12-08 12:26 Tom Tromey
2000-12-08 13:58 ` Fernando Nasser
2000-12-11 8:42 ` Fernando Nasser
2000-04-07 17:32 Tom Tromey
2000-04-10 9:02 ` Fernando Nasser
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=3A57ACA5.C336387E@redhat.com \
--to=fnasser@redhat.com \
--cc=bbranham@networkusa.net \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).