Opened 15 years ago
Closed 14 years ago
#24424 closed defect (worksforme)
emacs 23.1.1 Fatal error (10)Bus error with org mode
| Reported by: | a_green_gecko@… | Owned by: | drkp (Dan Ports) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.2 |
| Keywords: | Cc: | ||
| Port: | emacs |
Description
Mac OS X 10.5.8, XCode 3.1 (Beta)
I've compiled emacs 23.1.1 and can consistent produce a "Fatal error (10)Bus error" error in org-mode (just ctrl-s to find a node and then move up/down with ctrl-n/p). Has anyone else seen this?
I tried running in gdb and got the stack:
Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000000 0x0001768e in next_element_from_display_vector () (gdb) where #0 0x0001768e in next_element_from_display_vector () #1 0x0001f075 in get_next_display_element () #2 0x0002bfab in display_line () #3 0x0002d41d in try_window () #4 0x0003591f in redisplay_window () #5 0x0003745e in redisplay_window_0 () #6 0x00124bfa in internal_condition_case_1 () #7 0x0001a5ad in redisplay_windows () #8 0x00031cd5 in redisplay_internal () #9 0x000322bc in redisplay_preserve_echo_area () #10 0x000059b6 in Fredisplay () #11 0x00126278 in Ffuncall () #12 0x001593e6 in Fbyte_code () #13 0x00126070 in funcall_lambda () #14 0x0012641b in Ffuncall () #15 0x001593e6 in Fbyte_code () #16 0x00126070 in funcall_lambda () #17 0x0012641b in Ffuncall () #18 0x001593e6 in Fbyte_code () #19 0x00126070 in funcall_lambda () #20 0x0012641b in Ffuncall () #21 0x001593e6 in Fbyte_code () #22 0x00126070 in funcall_lambda () #23 0x0012641b in Ffuncall () #24 0x001593e6 in Fbyte_code () #25 0x00126070 in funcall_lambda () #26 0x0012641b in Ffuncall () #27 0x00126c3a in apply1 () #28 0x001232f0 in Fcall_interactively () #29 0x00126278 in Ffuncall () #30 0x001264f8 in call3 () #31 0x000cfad1 in command_loop_1 () #32 0x00124e4a in internal_condition_case () #33 0x000bf9ed in command_loop_2 () #34 0x00124ae1 in internal_catch () #35 0x000bf854 in command_loop () #36 0x000bf946 in recursive_edit_1 () #37 0x000c79dd in Frecursive_edit () #38 0x000bf508 in main () (gdb)
Change History (5)
comment:1 Changed 15 years ago by mf2k (Frank Schima)
| Owner: | changed from macports-tickets@… to dports@… |
|---|---|
| Port: | emacs added |
comment:2 Changed 15 years ago by drkp (Dan Ports)
comment:3 Changed 14 years ago by jmroot (Joshua Root)
| Owner: | changed from dports@… to dports@… |
|---|
comment:4 Changed 14 years ago by a_green_gecko@…
Ooop, my apologies for the delay. This was with console-mode emacs. I run emacs inside a Terminal with TERM=xterm-color. I'm getting org-mode directly from orgmode.org
Unfortunately, the video chip on the laptop I had been using died and I've switched laptops. I'm now using emacs 23.2.1 on MacOS 10.6.3 and can't duplicate the problem with org-mode 6.36
.a
comment:5 Changed 14 years ago by drkp (Dan Ports)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Glad to hear the problem is resolved one way or the other. ;-) Feel free to reopen if you run into it again.
BTW, the org-mode port may help save you some effort keeping up to date with the (surprisingly frequent) org-mode updates.
Haven't experienced this one (and I use org-mode myself).
Is this emacs +x11/gtk, or console-mode, or emacs-app? Are you using org-mode from emacs or from the org-mode port?