From: Richard Walter <Richard.Walter@hob.de>
To: Daniel Jacobowitz <drow@false.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb crashes with Solaris 10 x86
Date: Thu, 10 Nov 2005 08:51:00 -0000 [thread overview]
Message-ID: <4373076F.F4EA65D1@hob.de> (raw)
In-Reply-To: <20051109163524.GA23981@nevyn.them.org>
I installed the snapshot and run the program with gdb as you can see in
the output. I'm not familiar with debugging gdb itself, perhaps there
are further commands to examine the problem.
/home/walter/gw22 $ gdb
GNU gdb 6.3.90_20051110
Copyright 2004 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-pc-solaris2.10".
(gdb) set verbose on
(gdb) set prompt [top]
[top] exec-file /home/walter/gw22/NBIPGW08
[top] set args /home/walter/gw22/walter.xml
[top] run
Starting program: /home/walter/gw22/NBIPGW08
/home/walter/gw22/walter.xml
PR_SYSEXIT : Exit from a traced system call Exit from SYS_execve
PR_SYSEXIT : Exit from a traced system call Exit from SYS_execve
PR_FAULTED : Incurred a traced hardware fault FLTBPT: Breakpoint trap
PR_FAULTED : Incurred a traced hardware fault FLTTRACE: Trace trap
PR_FAULTED : Incurred a traced hardware fault FLTBPT: Breakpoint trap
Reading symbols from /usr/sfw/lib/libstdc++.so.6...(no debugging symbols
found)...done.
Reading symbols from
/usr/share/src/xerces-c-src_2_6_0_gcc/lib/libxerces-c.so.26...(no
debugging symbols found)...done.
Reading symbols from /lib/libsocket.so.1...(no debugging symbols
found)...done.
Reading symbols from /lib/libnsl.so.1...(no debugging symbols
found)...done.
Reading symbols from /lib/libdl.so.1...
(no debugging symbols found)...done.
Reading symbols from /lib/libc.so.1...(no debugging symbols
found)...done.
Reading symbols from /lib/libm.so.2...(no debugging symbols
found)...done.
Reading symbols from /usr/sfw/lib/libgcc_s.so.1...(no debugging symbols
found)...done.
Reading symbols from /lib/libpthread.so.1...warning: Lowest section in
/lib/libpthread.so.1 is .dynamic at 00000074
(no debugging symbols found)...done.
Reading symbols from /lib/libgen.so.1...(no debugging symbols
found)...done.
PR_FAULTED : Incurred a traced hardware fault FLTTRACE: Trace trap
*********Programm Output***************
PR_FAULTED : Incurred a traced hardware fault FLTBOUNDS: Memory bounds
violation
Program received signal SIGSEGV, Segmentation fault.
0x0805676d in ?? ()
[top]
Daniel Jacobowitz schrieb:
>
> On Wed, Nov 09, 2005 at 04:43:42PM +0100, Richard Walter wrote:
> > The program has a configuration file in xml format.
> > -bash-3.00$ gdb programname
> > (gdb) run configfile.xml
> > --program outputs--
> > Segmentation Fault (core dumped)
> > -bash-3.00$
> >
> > If you need a transcript of the session i have to talk to the developer,
> > that he comments out his own program trace output.
>
> Sorry, but if that's all you have to go on, you will need to debug GDB
> to see where it is crashing.
>
> Your first step should be to try a snapshot of GDB:
> ftp://sourceware.org/pub/gdb/snapshots/branch/gdb.tar.bz2
>
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-10 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 14:54 Richard Walter
2005-11-09 14:59 ` Daniel Jacobowitz
2005-11-09 15:22 ` Richard Walter
2005-11-09 15:24 ` Daniel Jacobowitz
2005-11-09 15:54 ` Richard Walter
2005-11-09 16:35 ` Daniel Jacobowitz
2005-11-10 8:51 ` Richard Walter [this message]
2005-11-10 13:45 ` Daniel Jacobowitz
2005-11-10 16:09 ` Richard Walter
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=4373076F.F4EA65D1@hob.de \
--to=richard.walter@hob.de \
--cc=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).