From: Simon Richter <Simon.Richter@hogyros.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Stepping over longjmp presumably broken for glibc
Date: Fri, 23 Dec 2005 18:01:00 -0000 [thread overview]
Message-ID: <43AC3B63.7090705@hogyros.de> (raw)
In-Reply-To: <uek43iu5a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Hi,
Eli Zaretskii wrote:
> If glibc maintainers actively fight the debugger's ability to debug
> their code, we will never succeed in catching up with them. So I'd
> rather they stopped with that attitude and started cooperating with
> us. I can ask RMS to try to influence the glibc team, if you think
> this will help.
I think it's another issue of debug vs. non-debug binaries. Any debugger
will have a hard time finding the end of a higher-language construct in
a non-debug binary. A debug binary on the other hand should not intermix
constructs and take care to have enough hints for the debugger to find
out stuff. A glibc for debugging should hence store usable pointers, and
people should use a debug build when debugging the glibc.
Simon aka Captain Obvious
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2005-12-23 18:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 21:17 Daniel Jacobowitz
2005-12-23 3:32 ` Jim Blandy
2005-12-23 8:25 ` Eli Zaretskii
2005-12-23 13:20 ` Daniel Jacobowitz
2005-12-23 15:16 ` Eli Zaretskii
2005-12-23 15:20 ` Daniel Jacobowitz
2005-12-23 17:07 ` Eli Zaretskii
2005-12-23 17:09 ` Daniel Jacobowitz
2005-12-23 17:46 ` Eli Zaretskii
2005-12-23 18:01 ` Simon Richter [this message]
2005-12-24 11:59 ` Eli Zaretskii
2005-12-24 16:23 ` Daniel Jacobowitz
2005-12-24 16:36 ` Eli Zaretskii
2005-12-24 16:59 ` Daniel Jacobowitz
2005-12-26 4:06 ` Jim Blandy
2005-12-26 5:19 ` Eli Zaretskii
2005-12-27 4:24 ` Jim Blandy
2005-12-30 2:38 ` Daniel Jacobowitz
2005-12-30 9:32 ` Mark Kettenis
2005-12-30 16:25 ` Daniel Jacobowitz
2006-01-02 5:25 ` Jim Blandy
2006-01-06 19:43 ` Daniel Jacobowitz
2006-01-06 20:28 ` Jim Blandy
2006-01-06 20:36 ` Daniel Jacobowitz
2006-01-06 20:53 ` Jim Blandy
2006-01-06 21:27 ` Mark Kettenis
2006-01-06 21:28 ` Daniel Jacobowitz
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=43AC3B63.7090705@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=eliz@gnu.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