wd wrote:

A two-character string can't be THAT hard to decrypt.

Actually, the shorter the ciffer-text, the harder it is to decrypt.

Yes but 26*26 should be human-doable with context. So with the gcc
context you're quite directly at an identity encryption.

wd wrote:

Yes but 26*26 should be human-doable with context. So with the gcc context you're quite directly at an identity encryption.

True - except for:

jal wrote:

Mmm, nothing I can go on. I'm not very versed with gdb, (...)

So you and jal don't quite have the same context.

Context switch 😀

http://www.google.com/search?q=gcc+bt - nope :p

http://www.google.com/search?q=gdb+bt yeppe

gcc 4.3.3 (Ubuntu 4.3.3-5ubuntu4), on both systems.

JAL

Ok, pretty much totally lost now.

I added a simple LOG_MSG("start MSG_Add"); at the start of the MSG_Add function in messages.cpp, and this is what I get:

1Program received signal SIGSEGV, Segmentation fault.
2[Switching to Thread 0xb77386e0 (LWP 5590)]
30xb7d91969 in _nc_printf_string () from /lib/libncurses.so.5
4(gdb) bt
5#0  0xb7d91969 in _nc_printf_string () from /lib/libncurses.so.5
6#1  0xb7d8d464 in vwprintw () from /lib/libncurses.so.5
7#2  0xb7d8d57b in wprintw () from /lib/libncurses.so.5
8#3  0x0813688b in DEBUG_ShowMsg (format=0x83835ad "start MSG_Add") at debug_gui.cpp:79
9#4  0x083402f8 in MSG_Add (_name=0xac553bc "CONFIG_FULLSCREEN", _val=0xac5536c "Start dosbox directly in fullscreen.") at messages.cpp:48
10#5  0x083469bb in Property::Set_help (this=0xac552f8, in=@0xbfc98858) at setup.cpp:223
11#6  0x081d2717 in Config_Add_SDL () at sdlmain.cpp:1469
12#7  0x081d6f97 in main (argc=Cannot access memory at address 0x0
13) at sdlmain.cpp:1655

There must be something seriously fucked up somewhere...

JAL

Well could be that at this point the ncurses window is not set up so it
crashes badly (though unrelated to the problem). You could set a breakpoint
there though.

wd wrote:

Well could be that at this point the ncurses window is not set up so it crashes badly (though unrelated to the problem). You could set a breakpoint there though.

Yeah, could try, but it's getting mightely complex for a simple soul like me 😀. Well, given the time I could probably figure it out, but that's something I unfortunately don't have too much...

JAL

try resizing the terminal manually to something large before starting dosbox

Qbix wrote:

try resizing the terminal manually to something large before starting dosbox

Mmm, weird, not just a large size but any size seems to work, as long as the window isn't maximized. When redirecting output to a file it also doesn't crash, btw (although the debugger is not of much use then 😀). Is this some obscure known bug?

JAL

not known, but sometimes a terminal doesn't resize correctly, but if it works with any size as long it isn't maximized than I don't really know

Qbix wrote:

not known, but sometimes a terminal doesn't resize correctly, but if it works with any size as long it isn't maximized than I don't really know

Well, at least it seems it isn't really a DOSBox problem, and there's a simple workaround. Thanks for pointing me in the right direction! (And thanks to wd as well, of course.)

JAL