| 1 |
Arcady Genkin wrote: |
| 2 |
> Dave Lee <davel@××××××.com> writes: |
| 3 |
> |
| 4 |
> > Has anyone been able to figure out why xemacs segfaults on startup? As |
| 5 |
> > mentioned before, if you are emerge-ing something, than xemacs will |
| 6 |
> > actually run w/o segfaulting. This is strange behavior. TIA, Dave |
| 7 |
> |
| 8 |
> Which version? |
| 9 |
|
| 10 |
both 21.1.whatever and 21.4.6 |
| 11 |
|
| 12 |
> Have you tried |
| 13 |
> |
| 14 |
> xemacs -debug-init |
| 15 |
> xemacs -vanilla |
| 16 |
> |
| 17 |
> Also try running in the terminal with |
| 18 |
> |
| 19 |
> xemacs -nw |
| 20 |
|
| 21 |
I did try -vanilla and -norc, but not the others. I'll see what they do |
| 22 |
for me. |
| 23 |
|
| 24 |
> Perhaps these would help you to pin-point the problem... |
| 25 |
|
| 26 |
I dont know, would it? Can anybody see why xemacs would run just fine |
| 27 |
when I am in the process of compiling something else, but when I am not |
| 28 |
compiling anything it segfaults immediately. |
| 29 |
|
| 30 |
I did try to run strace on xemacs, and although I dont have the results at |
| 31 |
hand to cut and paste, the segfault was happening after a bunch of stat |
| 32 |
calls that were looking for default.{elc,el,} but when I am compiling |
| 33 |
something nothing happens here other than ENOENT. |
| 34 |
|
| 35 |
Dave |
Archives