#28900 closed defect (fixed)
memory fault in xterm due to xorg-libXt 1.1.0
| Reported by: | erg@… | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ||
| Port: | xorg-libXt |
Description
I recently upgraded to xterm 269. When I now run it, it immediately reports a memory fault. The crash occurs on line 1984 of main.c in the call to XtOpenApplication:
Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0xffffffe4 0x0015f7cd in XtOpenApplication ()
This is on osx 10.5.8.
Attachments (1)
Change History (16)
comment:1 Changed 14 years ago by jmroot (Joshua Root)
| Owner: | changed from macports-tickets@… to jeremyhu@… |
|---|---|
| Port: | xterm added |
comment:2 follow-up: 3 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Can you please attach the crash report?
comment:3 Changed 14 years ago by erg@…
Replying to jeremyhu@…:
Can you please attach the crash report?
I am not exactly sure what you want. If I run it, I get:
s) /opt/local/bin/xterm
Memory fault
s)
The description in the original report has the details given by gdb.
If there is something else you need, please let me know.
comment:4 follow-up: 5 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Please attach the crash log. It's usually in a window that pops up when the crash occurs, or you can find it in ~/Library/Logs/DiagnosticReports or ~/Library/Logs/CrashReporter depending on your OS version.
Changed 14 years ago by erg@…
| Attachment: | xterm_2011-03-26-105748_snares.crash added |
|---|
comment:5 Changed 14 years ago by erg@…
Replying to jeremyhu@…:
Please attach the crash log. It's usually in a window that pops up when the crash occurs, or you can find it in ~/Library/Logs/DiagnosticReports or ~/Library/Logs/CrashReporter depending on your OS version.
Done. Thanks. I was unaware of those reports.
comment:6 follow-up: 7 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
That backtrace is bizarre... my guess is the stack got corrupted and blew away the stored %ebp ...
comment:7 Changed 14 years ago by erg@…
Replying to jeremyhu@…:
That backtrace is bizarre... my guess is the stack got corrupted and blew away the stored %ebp ...
If there is anything I can do to help, let me know. Obviously, the program doesn't get very far.
comment:8 Changed 14 years ago by erg@…
The problem appears to be in xorg-libXt @1.1.0_0. I deactivated that and re-activated xorg-libXt @1.0.9_0, and the problem has gone away.
comment:9 follow-up: 12 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Please update to 1.1.1
comment:10 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:11 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Port: | xorg-libXt added; xterm removed |
|---|
comment:12 Changed 14 years ago by erg@…
Replying to jeremyhu@…:
Please update to 1.1.1
How would I update to 1.1.1? At present, macports only appears to offer 1.1.0. Thanks.
comment:13 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
port -v sync && sudo port -v upgrade outdated
comment:15 Changed 14 years ago by jmroot (Joshua Root)
| Summary: | memory fault in xterm → memory fault in xterm due to xorg-libXt 1.1.0 |
|---|
Please remember to fill in the Port field and cc the maintainer.