wineserver not reading config files

[Saulius Krasuckas]

(Subject was: wineinstall problems at creation of config-files)

Ok, today I got less lazy and found function of interest:
/usr/src/wine-cvs/wine/server/registry.c:1114:    fprintf( stderr, "Line %d: %s '%s'\n", info->line, err, info->buffer );

Function name seems to be "file_read_error".

Plainly running /usr/local/bin/wineserver shows Line-errors, but killing
it (via winserver -k) and running it via gdb stops emitting mentioned
Line-errors to output:

[s2@katleriai s2]$ gdb --quiet /usr/local/bin/wineserver
(gdb) break file_read_error
Breakpoint 1 at 0x805b91e: file registry.c, line 1114.
(gdb) r
Starting program: /usr/local/bin/wineserver

Program exited with code 02.
(gdb)

Maybe there is some complex methods on debugging wineserver's binary? I am
asking for help on that.

PS I had refreshed src from the CVS and recompiled Wine before trying to 
debug it.

[Kevin Koltzau]

On Friday 30 April 2004 06:31 am, Saulius Krasuckas wrote:
> (Subject was: wineinstall problems at creation of config-files)
>
> Ok, today I got less lazy and found function of interest:
> /usr/src/wine-cvs/wine/server/registry.c:1114:    fprintf( stderr, "Line %d: %s '%s'\n", info->line, err, info->buffer );
>
> Function name seems to be "file_read_error".

I was having this problem too, I just stuck
[HKLM\Machine\Software\Wine\Wine\Config]
at the top of my config file and that seemed to fix it

[Saulius Krasuckas]

On Fri, 30 Apr 2004, Kevin Koltzau wrote:
> I was having this problem too, I just stuck
> [HKLM\Machine\Software\Wine\Wine\Config] at the top of my config
> file and that seemed to fix it

Right, Kevin, it fixes my Wine too. Thanks. Hope Alexandre will fix it
soon.

[hatky]

> I was having this problem too, I just stuck
> [HKLM\Machine\Software\Wine\Wine\Config]
> at the top of my config file and that seemed to fix it

Oh, 1,000 10x my lord

Can someone patch the installed config to have this?

[hatky]

> I was having this problem too, I just stuck
> [HKLM\Machine\Software\Wine\Wine\Config]
> at the top of my config file and that seemed to fix it

:(,
now I get just the segfault .......

[hatky]

On Friday 30 April 2004 13:31, Saulius Krasuckas wrote:
> (Subject was: wineinstall problems at creation of config-files)
>
> Ok, today I got less lazy and found function of interest:
> /usr/src/wine-cvs/wine/server/registry.c:1114:    fprintf( stderr, "Line %d:

%s '%s'\n", info->line, err, info->buffer );
> Function name seems to be "file_read_error".
>
> Plainly running /usr/local/bin/wineserver shows Line-errors, but killing
> it (via winserver -k) and running it via gdb stops emitting mentioned
> Line-errors to output:
>
> [s2@katleriai s2]$ gdb --quiet /usr/local/bin/wineserver
> (gdb) break file_read_error
> Breakpoint 1 at 0x805b91e: file registry.c, line 1114.
> ..........

I have your problem also but I think the segfault post is about the same 
thing: 
http://www.winehq.org/hypermail/wine-devel/2004/04/0806.html

basicly he says this patch is the problem:
http://cvs.winehq.org/patch.py?id=12187

sounds right by what the patch is about, didn't try reversing it yet

[Saulius Krasuckas]

On Fri, 30 Apr 2004, hatky wrote:
> basicly he says this patch is the problem:
> http://cvs.winehq.org/patch.py?id=12187
>
> sounds right by what the patch is about, didn't try reversing it yet

Hm, maybe.
Though I finally figured out on how to debug wineserver:

[s2@katleriai s2]$ gdb -q --args /usr/local/bin/wineserver -f -p
(gdb) break file_read_error
Breakpoint 1 at 0x805b91e: file registry.c, line 1114.
(gdb) r
Starting program: /usr/local/bin/wineserver -f -p

Breakpoint 1, file_read_error (err=0x806d146 "Malformed key", 
info=0xbffffa74) at registry.c:1114
1114        fprintf( stderr, "Line %d: %s '%s'\n", info->line, err, info->buffer );
(gdb) bt
#0  file_read_error (err=0x806d146 "Malformed key", info=0xbffffa74) at registry.c:1114
#1  0x0805bd0d in load_key (base=0x80771d0, buffer=0x8077261 "wine]", flags=1, prefix_len=2, info=0xbffffa74, 
    default_modif=1083324039) at registry.c:1234
#2  0x0805c390 in load_keys (key=0x80771d0, f=0x8076e00) at registry.c:1430
#3  0x0805c56a in init_registry () at registry.c:1508
#4  0x08052fc8 in main (argc=3, argv=0xbffffb14) at main.c:132
#5  0x42015967 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) c
Continuing.
Line 8: Malformed key '[wine]'

Breakpoint 1, file_read_error (err=0x806d1ac "Error creating key", 
info=0xbffffa74) at registry.c:1114
1114        fprintf( stderr, "Line %d: %s '%s'\n", info->line, err, info->buffer );
(gdb) bt
#0  file_read_error (err=0x806d1ac "Error creating key", info=0xbffffa74) at registry.c:1114
#1  0x0805c3ac in load_keys (key=0x80771d0, f=0x8076e00) at registry.c:1431
#2  0x0805c56a in init_registry () at registry.c:1508
#3  0x08052fc8 in main (argc=3, argv=0xbffffb14) at main.c:132
#4  0x42015967 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) c 
Continuing.
Line 8: Error creating key '[wine]'

I wonder now what does "+ 1" operation do inside the load_keys() in
server/registry.c:

if (prefix_len == -1) prefix_len = get_prefix_len( key, p + 1, &info );
            if (!(subkey = load_key( key, p + 1, flags, prefix_len, &info, default_modif )))

Last mod of the file is three months old, at least.