On Sun, Sep 08, 2013 at 10:13:13AM +0100, Robert Swindells wrote: > > Thomas Klausner wrote: > >On Sun, Sep 08, 2013 at 11:59:51AM +0400, Valeriy E. Ushakov wrote: > >> Haven't you or someone else complained about problems with emacs24 > >> vs. environ a few months ago? > > >This is still the same issue I've been seeing and reporting for > >months. There is a random element in the backtrace (sometimes it even > >works! perhaps my stack limit test was a random success), but it > >usually ends in getenv and below, trying some to find some language > >environment stuff. > > If you run: > > % nm emacs | sort > lst > > What variables are just below environ in memory ?
... 0000000000c16678 b data_space_start 0000000000c16680 b lim_data 0000000000c16688 b utimensat_works_really 0000000000c1668c b lutimensat_works_really 0000000000c16690 b localtime_offset 0000000000c166a0 B environ 0000000000c166c0 B last_nonminibuf_frame 0000000000c166e0 B space_glyph 0000000000c16710 B updated_area 0000000000c16714 B frame_garbaged 0000000000c16715 B fonts_changed_p 0000000000c16718 B Qdisplay_table ... Thomas
