So I've run into an interesting problem lately. Something that I've done has completely hosed the msg_area.scan_ptr, potentially in multiple message areas. I'm not sure what's caused it but I'm pretty sure that I've got rid of it. 'Course either way I still need to be able to reset it to a 'sane' value so that I can resume testing this software with this login, or be able to recover a different login should I start using it.
Here's a little dump of the debug information that I've got. Please note that sBoard is a msg_area object and mBase is a MsgBase object.

-=-=-=-=-=-

Babble> Using node #: 1
Read backward
Entered scanSub(); forward = false user.cursub: topegrpbabble
sBoard.code: topegrpbabble
Opened: topegrpbabble allegedly . . .
mBase.error:
sBoard.scan_ptr = 2060051968
mBase.first_msg = 1
mBase.total_msgs = 13
mBase.last_msg = 13
Inc: -1 based on forward
In main scanSub() loop tmpPtr: 2060051969 total_msgs: 13 is_open: yes
DEBUG: Next Msg
End of scanSub() main loop
tmpPtr: 2060051968 inc: -1
rcChoice() called w/base: topegrpbabble ndx: 2060051968
Using node #: 1
Reopened topegrpbabble to check for updates

[Babble> msg #2060051969 (-2060051955 remaining)] Read cmd ->

-=-=-=-=-=-
If anybody has any ideas on how to reset that number easily (other than in code, I'm hoping) to something sane (ie in this case 1-13), I would very much appreciate it. I think at one point I just didn't have the edge case defined well enough and it ran off to the negative overflow area of a long when I was doing a backwards message scan.
Any ideas appreciated. Thanks for your time.

-D/K

---
Borg Burgers: We do it our way; your way is irrelevant.
■ Synchronet ■ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

Re: Current message pointer corrupted for user?
By: Khelair to All on Sun May 31 2015 04:26 pm

So I've run into an interesting problem lately. Something that I've done has completely hosed the msg_area.scan_ptr, potentially in multiple message areas. I'm not sure what's caused it but I'm pretty sure that I've got rid of it. 'Course either way I still need to be able to reset it to a 'sane' value so that I can resume testing this software with this login, or be able to recover a different login should I start using it.
Here's a little dump of the debug information that I've got. Please note that sBoard is a msg_area object and mBase is a MsgBase object.

-=-=-=-=-=-

Babble> Using node #: 1
Read backward
Entered scanSub(); forward = false user.cursub: topegrpbabble
sBoard.code: topegrpbabble
Opened: topegrpbabble allegedly . . .
mBase.error:
sBoard.scan_ptr = 2060051968
mBase.first_msg = 1
mBase.total_msgs = 13
mBase.last_msg = 13
Inc: -1 based on forward
In main scanSub() loop tmpPtr: 2060051969 total_msgs: 13 is_open: yes DEBUG: Next Msg
End of scanSub() main loop
tmpPtr: 2060051968 inc: -1
rcChoice() called w/base: topegrpbabble ndx: 2060051968
Using node #: 1
Reopened topegrpbabble to check for updates

[Babble> msg #2060051969 (-2060051955 remaining)] Read cmd ->

-=-=-=-=-=-
If anybody has any ideas on how to reset that number easily (other than in code, I'm hoping) to something sane (ie in this case 1-13), I would very much appreciate it.

That message number *could* be valid. Each message imported into the message base or posted gets a unique number. So just because you currently have 13 messages does not mean their message numbers (for internal use) would be 1 through 13.

I think at one point I just didn't have the edge case
defined well enough and it ran off to the negative overflow area of a long when I was doing a backwards message scan.
Any ideas appreciated. Thanks for your time.

You can use the &P command from the main menu of the default command shell to set/reset your msg scan pointers.

digital man

Synchronet "Real Fact" #61:
Name of Synchronet PCMS compiler/language "Baja" was coined by Michael Swindell.
Norco, CA WX: 57.2°F, 94.0% humidity, 2 mph SE wind, 0.00 inches rain/24hrs