From: Mark Kettenis <kettenis@chello.nl>
To: m.mueller99@kay-mueller.de
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: patch 1 for Sun C compiled target programs
Date: Fri, 18 Jun 2004 21:47:00 -0000 [thread overview]
Message-ID: <200406182147.i5ILlM3f001498@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <40D08A0C.1050606@kay-mueller.de> (message from Michael Mueller on Wed, 16 Jun 2004 19:57:32 +0200)
Date: Wed, 16 Jun 2004 19:57:32 +0200
From: Michael Mueller <m.mueller99@kay-mueller.de>
Setting a breakpoint on a function name or on the first line of a
function doesn't work for Sun C compiled target programs (32 and 64
bit). I verified this against these compiler versions:
Sun C 5.5 2003/03/12
Forte Developer 7 C 5.4 2002/03/09
Sun WorkShop 6 update 2 C 5.3 2001/05/15
Sun WorkShop 6 2000/04/07 C 5.1
Ah yes. I knew about this. Just forgotten all about it. The funny
code you're seeing is there to work around a bug in GCC 2.95. GDB
fiddles a bit with the line number info trying to fix the breakage.
It's completely bogus, and should go since it messes up real-world
debugging with GCC 2.95 too. Unfortunately doing so will mess up the
testsuite results when using GCC 2.95 :-(.
I'll try to get this fixed before the 6.2 release. Thanks for giving
me a bit more ammunition for getting this change accepted by the rest
of the crowd.
Mark
next prev parent reply other threads:[~2004-06-18 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 17:58 Michael Mueller
2004-06-18 21:47 ` Mark Kettenis [this message]
2004-06-18 23:27 ` Daniel Jacobowitz
2004-06-21 13:09 ` Michael Mueller
2004-07-10 21:06 ` Mark Kettenis
2004-07-12 10:25 ` Michael Mueller
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=200406182147.i5ILlM3f001498@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=m.mueller99@kay-mueller.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