From: "Dieter Stüken" <stueken@conterra.de>
To: gdb@sources.redhat.com
Subject: 'next' command broken on sparc
Date: Wed, 16 Feb 2005 02:10:00 -0000 [thread overview]
Message-ID: <421208A4.7060607@conterra.de> (raw)
I frequently observe the 'next' command not to stop
at then next line. Instead the program continues to the end.
Similar problems are reported some time ago in conjunction
with mips, threads or shlibs.
But I'm working on solaris, using:
GNU gdb 6.3
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 "sparc-sun-solaris2.8".
and:
> gcc -v
Reading specs from /share/unix/solaris/8/pakete/gcc-3.4.3-64/lib/gcc/sparc64-sun-solaris2.8/3.4.3/specs
Configured with: ../gcc-3.4.3/configure --prefix=/share/unix/solaris/8/pakete/gcc-3.4.3-64 sparc64-sun-solaris2.8
Thread model: posix
gcc version 3.4.3
It happens in a bigger project, and I could not narrow it down
to special situations. It seems to happen quite randomly to me.
Thus I don't have any small example code by now.
I have to use shared libs, which also require threads
(although I don't use any threads explicitly)
Is this a known problem? Can I avoid it?
Dieter.
--
Dieter Stüken, con terra GmbH, Münster
stueken@conterra.de
http://www.conterra.de/
(0)251-7474-501
next reply other threads:[~2005-02-15 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 2:10 Dieter Stüken [this message]
2005-02-16 4:20 ` Mark Kettenis
2005-02-17 19:17 ` Dieter Stüken
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=421208A4.7060607@conterra.de \
--to=stueken@conterra.de \
--cc=gdb@sources.redhat.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