Re: Odd build behavior?

[Bob Gilson]

e.sammer wrote:

> All:
>
> I am getting NSRangeExceptions when making a call to [NSUnarchiver 
> unarchiveObjectWithData:] as it tries to read the typestream. With 
> some help from some folks on #gnustep, we tried to track it down to no 
> avail.
>
> Here's what's strange... What _does_ fix the problem is compiling with 
> debug=yes. Any other build "styles" (i.e. debug=no, warn=blah, etc.) 
> yeild a nonfunctional binary with the above problem. Of course, I 
> can't say for sure if this is a GS thing (I don't think it is) but if 
> anyone else sees this behavior in GS, please let me know as I do need 
> to build non-debugging versions of my work at some point.
>
> One of the things that may be a contributing factor (this is shotgun 
> debugging) is that I compiled gcc 3.1 but did not update glibc anytime 
> recently which just feels wrong. Either way, it's really really odd 
> and if anyone has an idea about what it could be... etc, etc...
>
> Thanks in advance.

I've installed gcc 3.1 on RH 7.1 with glibc-2.2.2-10.  My most recent 
update from cvs was a couple days ago. I've seen the same error you 
describe. And I've seen another when starting gdnc and gpbs:

[bgilson@wallace bgilson]$ 2002-05-24 13:08:50.477 gdnc[1750] unable to 
bind to port 191.0.0.0:0 - Cannot
assign requested address
2002-05-24 13:08:50.524 gdnc[1750] gdnc - unable to register with name 
server - quiting.

gdomap is starting without error messages.

My network is 192.168.1.0 and 191.0.0.0 doesn't exist in the source 
code. If I build base with debug=yes, then gdnc and gpbs start without 
error messages. Other duties have kept me from making more progress. Rats.

Hope this helps,
Bob