[DiscordArchive] is that actual byte code of server executable ?
[DiscordArchive] is that actual byte code of server executable ?
Original source
is that actual byte code of server executable ?
rektbyfaith
06-12-2024, 01:12 PM #1Archived author: Rymercyble • Posted: 2024-06-12T13:12:46.908000+00:00
Original source
is that actual byte code of server executable ?
Original source
Yeah
rektbyfaith
06-12-2024, 01:12 PM #2Archived author: Qeme • Posted: 2024-06-12T13:12:59.833000+00:00
Original source
Yeah
Original source
then im pretty confused as to what are u even doing there if there is issue with core why arent u using debug ?
rektbyfaith
06-12-2024, 01:14 PM #3Archived author: Rymercyble • Posted: 2024-06-12T13:14:12.538000+00:00
Original source
then im pretty confused as to what are u even doing there if there is issue with core why arent u using debug ?
Original source
I'm running it with fs memory sanitization. The gdb analysis shows
```bash Thread 7 "worldserver" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffefdff640 (LWP 277989)]
0x0000555557bfb162 in atomic_load_p (a=0x1ffff8, mo=atomic_memory_order_relaxed) at /root/azc-classic-plus/deps/jemalloc/include/jemalloc/internal/atomic.h:62```
I tried running valgrind to check for leaks but doesn't seem like it wants to accept the debug info. I love the error too:
```bash
==278423== Valgrind: "/root/aazcore2/bin/worldserver"
==278423==
==278423== Valgrind: debuginfo reader: Possibly corrupted debuginfo file.
==278423== Valgrind: I can't recover. Giving up. Sorry.
==278423==
```
rektbyfaith
06-12-2024, 01:19 PM #4Archived author: Qeme • Posted: 2024-06-12T13:19:02.414000+00:00
Original source
I'm running it with fs memory sanitization. The gdb analysis shows
```bash Thread 7 "worldserver" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffefdff640 (LWP 277989)]
0x0000555557bfb162 in atomic_load_p (a=0x1ffff8, mo=atomic_memory_order_relaxed) at /root/azc-classic-plus/deps/jemalloc/include/jemalloc/internal/atomic.h:62```
I tried running valgrind to check for leaks but doesn't seem like it wants to accept the debug info. I love the error too:
```bash
==278423== Valgrind: "/root/aazcore2/bin/worldserver"
==278423==
==278423== Valgrind: debuginfo reader: Possibly corrupted debuginfo file.
==278423== Valgrind: I can't recover. Giving up. Sorry.
==278423==
```
Original source
So far memory santiziation gives me the only readable pointer tbh. I'm not great at this stuff.
rektbyfaith
06-12-2024, 01:20 PM #5Archived author: Qeme • Posted: 2024-06-12T13:20:58.431000+00:00
Original source
So far memory santiziation gives me the only readable pointer tbh. I'm not great at this stuff.
Original source
i would still try and run it in IDE with debugger even though memory corruption could shift references and create nonsense callstack maybe u would get lucky
rektbyfaith
06-12-2024, 01:21 PM #6Archived author: Rymercyble • Posted: 2024-06-12T13:21:19.602000+00:00
Original source
i would still try and run it in IDE with debugger even though memory corruption could shift references and create nonsense callstack maybe u would get lucky
1 Guest(s)
1 Guest(s)