From: Mark Kettenis <kettenis@gnu.org>
To: stueken@conterra.de
Cc: gdb@sources.redhat.com
Subject: Re: 'next' command broken on sparc
Date: Wed, 16 Feb 2005 04:20:00 -0000 [thread overview]
Message-ID: <200502160207.j1G27wwf012748@copland.sibelius.xs4all.nl> (raw)
In-Reply-To: <421208A4.7060607@conterra.de> (message from =?ISO-8859-1?Q?Dieter_St=FCken?= on Tue, 15 Feb 2005 15:35:16 +0100)
Date: Tue, 15 Feb 2005 15:35:16 +0100
From: =?ISO-8859-1?Q?Dieter_St=FCken?= <stueken@conterra.de>
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.
I doubt that this is related to the MIPS issue. Unfortunately it's
not easy to establish what the cause is. I noticed that you use gcc
3.4.3. It might be that the compiler is optimizing in ways that GDB
looses track. If you can't produce a smallish example that shows the
problem, can you provide me with the disassembled code from the
function where things go wrong, and the functions that are called by
that function around that point?
Mark
next prev parent reply other threads:[~2005-02-16 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 2:10 Dieter Stüken
2005-02-16 4:20 ` Mark Kettenis [this message]
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=200502160207.j1G27wwf012748@copland.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=stueken@conterra.de \
/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