This is a problem with overland I just found... Seems to be crashing my mud, though I hadn't used minvoke till now. Appreciate any help you can give me.

The GDB Backtrace:

#0  0x081b4dcd in fix_maps (ch=0x87cadf8, victim=0x40190001) at overland.c:630
630                xSET_BIT( victim->act, ACT_ONMAP );
(gdb) bt
#0  0x081b4dcd in fix_maps (ch=0x87cadf8, victim=0x40190001) at overland.c:630
#1  0x080cadc7 in do_minvoke (ch=0x87cadf8, argument=0xbfb1c6f5 "1200" at act_wiz.c:3160
#2  0x0816de98 in interpret (ch=0x87cadf8, argument=0xbfb1c6f5 "1200" at interp.c:548
#3  0x0812193e in game_loop () at comm.c:864
#4  0x081237b1 in main (argc=5, argv=0xbfb1cbe4) at comm.c:533

The piece of code at line 630 overland.c (As you can see, I've been trying some stuff.)

      if( IS_NPC( victim ) && xIS_SET( victim->act, ACT_ONMAP) )
           xSET_BIT( victim->act, ACT_ONMAP );
/*         REMOVE_ACT_FLAG( victim, ACT_ONMAP ); */
      else if( !IS_NPC( victim ) && xIS_SET( victim->act, PLR_ONMAP ) )
         REMOVE_ACT_FLAG( victim, PLR_ONMAP );

So, my understanding is that this is supposed to check if the victim is being loaded on the map then it needs to ACT/PLR flags as such.

I am getting crashes when loading a mobile into a non-map room.

Just the backtrace provided isn't really helpful. There are several lines before the actual backtrace that actually tell you exactly what the issue is.

I'll admit, I'm not entirely familiar with the Overland system (mainly because I don't like that type of system in general), but if you're trying to load a mob into a non-map room. I don't think you want to be setting the ACT_ONMAP flag on them. Also, that check is making sure that they have the flag. So, if they already have it, why exactly would you want to set it on them? .........................
Owner/Coder -- Malevolent Whispers -- Development Phase - Not accepting players
Coder -- Star Wars: The Sith Wars -- Open Alpha - Players Welcome - Full System Re-writes Imminent.

I3 Contact: Kayle@SithWars

#0 0x081b4dcd in fix_maps (ch=0x87cadf8, victim=0x40190001) at overland.c:630

That's enough to know that something is corrupting the "victim" pointer. 0x40190001 doesn't appear to be a valid address. do_minvoke is likely passing it data that's not been properly initialized. .........................
PDNS-Admin | Sandbox | Arthmoor MUD Hosting Services | The Truth About Medievia: A Saga of Code Theft.

"The past was erased, the erasure was forgotten, the lie became truth." -- George Orwell, 1984

Thanks for the assist. I fixed the crashing by going into Minvoke and adding checks around the fix_maps call to check in the character doing the minvoke is on a map.

This seems to allow me to minvoke properly without crashing, though I am too afraid of trying it on a map just yet.