Opened 5 years ago
Last modified 3 years ago
#15251 new bug
KERN: PANIC: attempting to clone area "runtime_loader_seg1rw"
| Reported by: | bbjimmy | Owned by: | nobody |
|---|---|---|---|
| Priority: | high | Milestone: | Unscheduled |
| Component: | System | Version: | R1/Development |
| Keywords: | Cc: | anevilyak | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev 53368
Browsing the web
KERN: PANIC: attempting to clone area "runtime_loader_seg1rw"
the panic is continuable, but the system locks up after.
Attachments (1)
Change History (4)
by , 5 years ago
| Attachment: | syslog.old added |
|---|
comment:1 by , 5 years ago
| Cc: | added |
|---|---|
| Component: | - General → System |
I already made a change to make the runtime_loader debug area cloneable; and this seems to have been more than enough in most cases here (most uses of Debugger seem to be just fine following the changes.) So the fact that the SymbolLookup is trying to clone the "runtime_loader_seg1rw" is strange to me. Shouldn't all the information it wants be in the debug area? What is it looking for in there, and why only in this case?
comment:2 by , 5 years ago
As best I can tell from what little information is available here, the instruction pointer it was asked to resolve a symbol for was in that area, hence the attempt to clone it. More than that I can't tell you without looking at a dump of that segment, which I'm not in a position to do right now.
comment:3 by , 3 years ago
This is still a problem, though now it becomes a "dprintf" instead of a KDL.
I guess Debugger needs a mechanism to clone areas that should not otherwise be cloneable.
syslog shows two such panics