From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eirik@hackrat.com
Cc: jimb@red-bean.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Use mmap for symbol tables
Date: Tue, 31 Jan 2006 21:48:00 -0000 [thread overview]
Message-ID: <200601312147.k0VLlrxj011443@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <43DEB182.4020804@hackrat.com> (message from Eirik Fuller on Mon, 30 Jan 2006 16:38:26 -0800)
> Date: Mon, 30 Jan 2006 16:38:26 -0800
> From: Eirik Fuller <eirik@hackrat.com>
>
> > For inclusion in the public GDB sources, I'd want GDB's sensitivity to
> > the files being changed out from underneath it to be unaffected,
> > regardless of the details of peoples' build processes.
>
> Fair enough. Making the mmap patch a configure time option (not just
> detecting the presence of mmap, but requiring that use of mmap to be
> explictly enabled) would accomplish that. Or always compile it in if
> mmap is detected at configure time but leave it disabled by default.
> If it's available, but is enabled only by request, and if the associated
> risks are documented, I don't think GDB's ability to handle changed
> files is diminished in any meaningful sense.
Please be aware that even if a particular OS supports mmap(2), it may
not be able to mmap files on all filesystems. So you'll have to check
at runtime whether mmap is possible and if it fails fall back on the
old code that simply reads the file.
Mark
next prev parent reply other threads:[~2006-01-31 21:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 23:36 Eirik Fuller
2006-01-30 5:04 ` Jim Blandy
2006-01-30 11:44 ` Eirik Fuller
2006-01-30 18:07 ` Jim Blandy
2006-01-30 18:59 ` Eirik Fuller
2006-01-30 22:11 ` Jim Blandy
2006-01-31 0:38 ` Eirik Fuller
2006-01-31 1:49 ` Jim Blandy
2006-01-31 3:12 ` Eirik Fuller
2006-01-31 21:48 ` Mark Kettenis [this message]
2006-02-01 17:52 ` Eirik Fuller
2006-02-01 6:04 ` Michael Snyder
2006-01-30 11:34 ` Andrew STUBBS
2006-01-30 11:42 ` Corinna Vinschen
2006-01-30 11:48 ` Andrew STUBBS
2006-01-31 2:23 ` Daniel Jacobowitz
2006-01-31 3:31 ` Eirik Fuller
2006-01-31 3:38 ` Daniel Jacobowitz
2006-02-07 22:05 ` Eirik Fuller
2006-02-20 15:52 ` Daniel Jacobowitz
2006-01-31 5:28 ` Jim Blandy
2006-01-31 13:59 ` Daniel Jacobowitz
2006-01-31 4:40 David Anderson
2006-01-31 5:00 ` Eirik Fuller
2006-01-31 5:34 ` Jim Blandy
2006-01-31 14:00 ` Daniel Jacobowitz
2006-01-31 18:39 ` Jim Blandy
2006-02-01 18:11 ` Eirik Fuller
2006-01-31 17:45 ` David Anderson
2006-01-31 18:24 ` Jim Blandy
2006-01-31 4:53 David Anderson
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=200601312147.k0VLlrxj011443@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eirik@hackrat.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.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