Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - FallenTree

Pages: 1 [2] 3 4 ... 33
16
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 15, 2015, 12:40:30 AM »
I doubt that's the issue, telnet protocol will escape IAC automatically.

This confirm my suspicion, this is a libtelnet bug, which I have yet to have a grasp at.

17
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 13, 2015, 11:32:01 PM »
are you saying the crash is also happening in 3.0alpha8.1 ?

It looks like a libtelnet bug, which I have yet to figure out how it happens.

18
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 12, 2015, 09:28:54 PM »
can you also use addr2line to get correct line number from your above crash stacktrace ?

19
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 10, 2015, 09:24:38 AM »
You would need to do this :

ulimit -c unlimited && ./driver xxxx

Verify that driver startup without the warning.  And when it crash, send me the core.xxx file , together with the driver binary. I will be able to see what this is about.

Also , can you paste the crash log again?

20
Drivers / Re: Different CUSTOM_CRYPT
« on: November 09, 2015, 09:17:53 AM »
I would suggest you do some basic testing first, like creating a command in both new and old driver, output some known value and see how they differ. Then report back? Also,you could setup some code to capture user's raw password somewhere in the db, for a given period, then convert to new driver, automatically generate new password for those active users, and ensure they work fine.

For long inactive users, well, good luck to them, have them find you and reset password somehow.

21
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: November 09, 2015, 09:15:01 AM »
do you have core available?

22
Drivers / Re: Requesting assistance on converting
« on: November 01, 2015, 10:01:38 PM »
You can send me emails at sunyucong@gmail.com

Cheers.

23
Drivers / Re: Contributions to the driver
« on: October 29, 2015, 09:57:57 AM »
I think you misunderstood what bridging to other VM means, It means we can load script written in another language ,evaluate it in its own VM and provide syscall for it to access driver internals.

It doesn't mean we need to run LPC code in another VM, which I think it is certainly not worth it.

For example, you will be able to load a full LUA or JS script that calls EFUN to interact with users while accessing everything a normal LUA/JS vm can access.Think about the possibilities! Of course we need to implement a sort of two way communication channel, for apply to work. but in general I think it can work.

That's why I am not recommending working on LPC VM anymore, including garbage collectors. oname.cc does need a rewrite, that is fine.

I generally prefer to not introduce OOP into driver, since I havn't actually find a use for it,  Driver code is mostly in C-style,  I think it is better to leverage STL or other small C++ library and features to make it easier to maintainer and better written.  As for the style, just use your judgement, as long as it can be compiled with gcc 4.8+ , we will be fine.

24
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: October 28, 2015, 12:13:37 AM »
Perfect, now is ok!

Tomorrow i'll come back to this version for tests.

Thank you very much!

Great , how did it go? Assuming everything is working okay?

25
Drivers / Re: Contributions to the driver
« on: October 27, 2015, 06:50:56 AM »
Also, I think working on the VM is not that interesting, at least to me, other than digging out old issues.

My primary goal is to bridge the driver with LUA,  later maybe also JS.  Which is clearly a more lively VM.

26
Drivers / Re: Contributions to the driver
« on: October 27, 2015, 01:06:50 AM »
My suggestion is to start small, do something benign and get to know the code base first. You can start by rewriting global living hash table to use std::unordered_map , for example.

FluffOS is a living driver, new changes need to be compatible with old code or at least provide a migration pathway. If you want to implement something as big as JIT or mark-and-sweep, you need to be very familiar with the codebase to start with. Something I am still trying to do.

27
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: October 26, 2015, 09:51:36 AM »
Hello, i can't compile driver.

This has been fixed by the latest commit. Also, I think ive also fixed the crash, please try again.

28
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: October 21, 2015, 10:18:31 AM »
I am working on fixing that.

29
Drivers / Re: Contributions to the driver
« on: October 21, 2015, 10:18:13 AM »
well of course!, send a PR!

30
Drivers / Re: WIP: Fluffos 3.0 Alpha 9.0
« on: October 16, 2015, 10:37:38 AM »
Code: [Select]
Oct  8 14:30:13 driver[16245]: ...bin/driver(+0xd3745)[0x7fe44c731745]
Oct  8 14:30:13 driver[16245]: /lib/x86_64-linux-gnu/libc.so.6(+0x35180)[0x7fe449dcc180]
Oct  8 14:30:13 driver[16245]: ...bin/driver(+0xd2d70)[0x7fe44c730d70]
Oct  8 14:30:13 driver[16245]: ...bin/driver(+0xcfb28)[0x7fe44c72db28]
Oct  8 14:30:13 driver[16245]: ...bin/driver(+0xd192a)[0x7fe44c72f92a]
Oct  8 14:30:13 driver[16245]: ...bin/driver(telnet_recv+0x158)[0x7fe44c724968]
Oct  8 14:30:13 driver[16245]: ...bin/driver(_Z13get_user_dataP13interactive_t+0x571)[0x7fe44c74beb1]
Oct  8 14:30:13 driver[16245]: /usr/lib/libevent-2.1.so.5(+0x179ec)[0x7fe44a9799ec]
Oct  8 14:30:13 driver[16245]: /usr/lib/libevent-2.1.so.5(+0x2164f)[0x7fe44a98364f]
Oct  8 14:30:13 driver[16245]: /usr/lib/libevent-2.1.so.5(event_base_loop+0x4df)[0x7fe44a9841ff]
Oct  8 14:30:13 driver[16245]: ...bin/driver(_Z7backendP10event_base+0x26e)[0x7fe44c728a9e]
Oct  8 14:30:13 driver[16245]: ...bin/driver(main+0x457)[0x7fe44c680d37]
Oct  8 14:30:13 driver[16245]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fe449db8b45]
Oct  8 14:30:13 driver[16245]: ...bin/driver(+0x240b1)[0x7fe44c6820b1]
Oct  8 14:30:13 driver[16245]: ******** FATAL ERROR: SIGSEGV: Segmentation fault
Oct  8 14:30:13 driver[16245]: FluffOS driver attempting to exit gracefully.
Oct  8 14:30:13 driver[16245]: crash() in master called successfully.  Aborting.

You need to post whole startup-log  , and possibly put your driver binary somewhere for me to download and analyse.

For now is ok, but i'm sure that will crash again.

I'm thinking about it.

The error is in:
Code: [Select]
telnet_recv(ip->telnet, reinterpret_cast<const char *>(&buf[0]), num_bytes);

Is possible that ip->telnet was incorrect or NULL for some telnet client? (i doubt it...)

I could not reproduce the error.

Startup log:
Code: [Select]
========================================================================
Boot Time: Wed Oct 14 17:23:06 2015
FluffOS Version: 3.0-alpha9.0(git-944ee22-1443467939)@ (Linux/x86-64)
Jemalloc Version: 4.0.3-0-ge9192eacf8935e29fc62fddc2701f7942b1cc02c
Core Dump: No, Max FD: 65535
Command: ./driver ./config.rl
========================================================================
Processing config file: ./config.rl
* Config 'time to clean up' New Value: 7200
* Config 'time to reset' New Value: 1800
* Config 'time to swap' New Value: 1800
* Config 'evaluator stack size' New Value: 1000
* Config 'maximum evaluation cost' New Value: 1000000
* Config 'maximum call depth' New Value: 35
* Config 'maximum array size' New Value: 25000
* Config 'maximum mapping size' New Value: 15000
* Config 'maximum bits in a bitfield' New Value: 1200
* Config 'maximum byte transfer' New Value: 10000
* Config 'living hash table size' New Value: 100
* Config 'gametick msec' New Value: 100
* Config 'heartbeat interval msec' New Value: 2000
* Config 'sane sorting' New Value: 0
* Config 'trace' New Value: 0
* Config 'receive snoop' New Value: 0
* Config 'reverse defer' New Value: 1
* Config 'enable_commands call init' New Value: 0
* Config 'sprintf add_justified ignore ANSI colors' New Value: 0
* Config 'call_out(0) nest level' New Value: 10000
Initializing internal stuff ....
Event backend in use: epoll

I saw exactly the same crash happened on another MUD. I sent in some fixes yesterday, can you update it and see if it happens again?

Pages: 1 [2] 3 4 ... 33