Crashlog is a shi**

Fargariel

Fargariel

System.NullReferenceException: Object reference not set to an instance of an object at Server.ValorVirtue.Valor (Server.Mobile from, System.Object targ) [0x00007] in <36c77eed6cfe43e4959a3170c42ad28c>:0 at Server.ValorVirtue+InternalTarget.OnTarget (Server.Mobile from, System.Object targeted) [0x00000] in <36c77eed6cfe43e4959a3170c42ad28c>:0 at Server.Targeting.Target.Invoke (Server.Mobile from, System.Object targeted) [0x002b3] in <619d370d8e6b4dea85b10cb138e93855>:0 at Server.Network.PacketHandlers.TargetResponse (Server.Network.NetState state, Server.Network.PacketReader pvSrc) [0x00237] in <619d370d8e6b4dea85b10cb138e93855>:0 at Server.Network.MessagePump.HandleReceive (Server.Network.NetState ns) [0x001e6] in <619d370d8e6b4dea85b10cb138e93855>:0 at Server.Network.MessagePump.Slice () [0x00057] in <619d370d8e6b4dea85b10cb138e93855>:0 at Server.Core.Main (System.String[] args) [0x00571] in <619d370d8e6b4dea85b10cb138e93855>:0

Any solution for this under linux&mono? How to get NORMAL log? ;d
 
Fargariel said:
System.NullReferenceException: Object reference not set to an instance of an object at Server.ValorVirtue.Valor (Server.Mobile from, System.Object targ)
Click to expand...

This is the most relevant part, the method Server.ValorVirtue.Valor (Server.Mobile from, System.Object targ) has code in it that's causing the null reference.

You might get line numbers if you run in debug mode.

Not sure how else to pretty-up the logs on MONO, it definitely is indeed "a shit" lol.
 
Sometimes a little manual editing makes everything easier. Enter and tab right before every 'at'. I haven't the foggiest of how to make MONO do this automatically, however.

Code: 
System.NullReferenceException: Object reference not set to an instance of an object
   at Server.ValorVirtue.Valor (Server.Mobile from, System.Object targ) [0x00007] in <36c77eed6cfe43e4959a3170c42ad28c>:0
   at Server.ValorVirtue+InternalTarget.OnTarget (Server.Mobile from, System.Object targeted) [0x00000] in <36c77eed6cfe43e4959a3170c42ad28c>:0
   at Server.Targeting.Target.Invoke (Server.Mobile from, System.Object targeted) [0x002b3] in <619d370d8e6b4dea85b10cb138e93855>:0
   at Server.Network.PacketHandlers.TargetResponse (Server.Network.NetState state, Server.Network.PacketReader pvSrc) [0x00237] in <619d370d8e6b4dea85b10cb138e93855>:0
   at Server.Network.MessagePump.HandleReceive (Server.Network.NetState ns) [0x001e6] in <619d370d8e6b4dea85b10cb138e93855>:0
   at Server.Network.MessagePump.Slice () [0x00057] in <619d370d8e6b4dea85b10cb138e93855>:0
   at Server.Core.Main (System.String[] args) [0x00571] in <619d370d8e6b4dea85b10cb138e93855>:0
 
That was just an example, i have already found the reason but it tooked much more time than with normal crash log. I have no possibility to run on Windows and this is my biggest problem because i modify core a lot so crash happens.
 
You must log in or register to reply here.
Back