Re: Bizarre out of memory bug
Re: Bizarre out of memory bug
- Subject: Re: Bizarre out of memory bug
- From: Justin Walker <email@hidden>
- Date: Fri, 27 May 2005 08:53:46 -0700
Truly weird behavior...
On May 27, 2005, at 1:26, Tim Seufert wrote:
Things found through further experimentation:
[snip]
4. The bug goes away if I don't invoke Wilfredo Sanchez's example tcsh
setup (/usr/share/tcsh/examples/rc) in my .cshrc .
Before you hit gdb, have you tried isolating what in Fred's setup might
be causing the problem (e.g., 'echo Here I am >> log-file')? That may
narrow it down enough to ring bells (I know something like this has
happened with shell startup scripts, in a previous lifetime). My
archives don't
5. I still only get this when SSHing from the PowerBook to the G5.
Despite trying to configure the PowerBook with an identical login name
and UID/GID, identical network config, and identical .cshrc,
everything works fine when logging in to the PowerBook. Unless I
figure out what's unique about the G5's configuration, this may not be
easy to replicate reliably on other systems.
Could be a "good garbage vs. bad garbage" issue (on one system, you get
zeros in memory; on another, non-zero bits. If those bits are a
pointer, in one case "boom"; in the other, harmless junk).
I think my next step is to try to build tcsh with debugging symbols,
attach to it with GDB when I log in, and step through the code to see
exactly where things go wrong. I may also try to track down exactly
which part of the example rc causes the problem. (Presumably it's the
section which sets up completion.)
If you've never debugged one of these shells before, you might consider
an alternative: poke yourself in the eye with a sharp stick; it takes
less time, but gives you the same pain :-}
Andrew's suggestion to use ktrace is a good one. There was a similar
thread back in 2003 (Guiliano Gavazzi: "tcsh: Out of Memory") that
involved tcsh closing down an 'ssh' session (darwin-development list),
and he seemed to have nailed down the problem with ktrace.
Cheers,
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for General Semantics
--------
It's not whether you win or lose...
It's whether *I* win or lose.
--------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden