WineDbg : list of errors

[Sylvain Petreolle]

Hi,

Using WineDbg,
I have problems to attach to a process.
I start "winedbg".
then "walk process".
It gives reference to a W-process.

Trying attach to this process gives me error 5.
Where could i find more info on these error numbers ?

[***@snoop La 4ème Prophétie]$ winedbg
WineDbg starting... on pid 0
Wine-dbg>walk process
pid threads parent exe
0806ba80 4 00000000 ''
Wine-dbg>attach 0x806ba80
Can't attach process 806ba80: error 5
Wine-dbg>

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[l***@juno.com]

Post by Sylvain Petreolle
Hi,
Using WineDbg,
I have problems to attach to a process.
I start "winedbg".
then "walk process".
It gives reference to a W-process.
Trying attach to this process gives me error 5.
Where could i find more info on these error numbers ?
WineDbg starting... on pid 0
Wine-dbg>walk process
pid threads parent exe
0806ba80 4 00000000 ''
Wine-dbg>attach 0x806ba80
Can't attach process 806ba80: error 5
Wine-dbg>

[***@giftie wine]$ grep "Can't att" debugger/*.c
debugger/winedbg.c: DEBUG_Printf(DBG_CHN_MESG, "Can't attach process=
%lx:
error %ld\n", pid, GetLastError());

Well, I think you would look that up in include/winerror.c, since it is
printing a GLE number:

#define ERROR_ACCESS_DENIED 5

I can't duplicate it though, so I don't know what it is yet.

Lawson

I haven't lost my mind -- it's backed up on tape somewhere.

[l***@juno.com]

Post by l***@juno.com
Well, I think you would look that up in include/winerror.c, since it is

Oops, that is a typo for <wine>/include/winerror.h, ^^^ of course.

Lawson

[Sylvain Petreolle]

Using winedbg on processes that don't stop
after ending a program, I try to attach to.

WineDbg gives error 5 that says "access denied".
Don't understand, because these are my own processes
??

Post by Sylvain Petreolle

Post by Sylvain Petreolle
Using WineDbg,
I have problems to attach to a process.
I start "winedbg".
then "walk process".
It gives reference to a W-process.
Trying attach to this process gives me error 5.
Where could i find more info on these error

numbers ?

Post by Sylvain Petreolle
WineDbg starting... on pid 0
Wine-dbg>walk process
pid threads parent exe
0806ba80 4 00000000 ''
Wine-dbg>attach 0x806ba80
Can't attach process 806ba80: error 5

Well, I think you would look that up in
include/winerror.h, since it is
#define ERROR_ACCESS_DENIED
5

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Eric Pouech]

Post by Sylvain Petreolle
WineDbg gives error 5 that says "access denied".
Don't understand, because these are my own processes

see my previous answer: it's of no use to keep on screaming
if you don't read and answer the other posts
another possibility, your process actually crashed, which
triggers the opening of the debugger, which somehow gets
stucked and hangs any other debugging tentative
how to know? try attaching with gdb (using the unix pid, from
ps). if it succeeds, then the error is somewhere else

A+

[Sylvain Petreolle]

Post by Sylvain Petreolle
WineDbg gives error 5 that says "access denied".

Post by Sylvain Petreolle
Don't understand, because these are my own

processes
see my previous answer: it's of no use to keep on
screaming
if you don't read and answer the other posts
another possibility, your process actually crashed,
which
triggers the opening of the debugger, which somehow
gets
stucked and hangs any other debugging tentative
how to know? try attaching with gdb (using the unix
pid, from
ps). if it succeeds, then the error is somewhere
else

[***@snoop La 4ème Prophétie]$ wine t4c.exe
(i use the program and then quit, no error messages)
[***@snoop La 4ème Prophétie]$
[***@snoop La 4ème Prophétie]$ps -ef |grep "wine"
syl 26358 1 2 20:48 ? 00:00:00
wineserver
syl 26362 1 0 20:48 pts/3 00:00:00 wine
--winver=winme t4c
syl 26363 1 0 20:48 pts/3 00:00:00 wine
--winver=winme t4c
syl 26364 1 0 20:48 pts/3 00:00:00 wine
--winver=winme t4c
syl 26366 25437 0 20:48 pts/3 00:00:00 grep
wine

[***@snoop La 4ème Prophétie]$ gdb
GNU gdb Red Hat Linux (5.1-1)
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
Public License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-redhat-linux".
(gdb) attach 26364
Attaching to process 26364
ptrace: Operation not permitted.



___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Eric Pouech]

syl 26358 1 2 20:48 ? 00:00:00 wineserver
syl 26362 1 0 20:48 pts/3 00:00:00 wine --winver=winme t4c
syl 26363 1 0 20:48 pts/3 00:00:00 wine --winver=winme t4c
syl 26364 1 0 20:48 pts/3 00:00:00 wine --winver=winme t4c
syl 26366 25437 0 20:48 pts/3 00:00:00 grep wine
(gdb) attach 26364
Attaching to process 26364
ptrace: Operation not permitted.

does it give the same type of error on 26362 and 26363? (likely)

what you can do now is trace what happens at the server level
(-debugmsg +server), and look for:
- either exception handling
- debug operation
and check what fails

A+

[Sylvain Petreolle]

Post by Eric Pouech

Post by Sylvain Petreolle

Post by Sylvain Petreolle
(gdb) attach 26364

Attaching to process 26364
ptrace: Operation not permitted.

does it give the same type of error on 26362 and
26363? (likely)

would have see it you didn't say me to try this.
only one of the 3 processes refuses gdb attach.

Post by Eric Pouech
what you can do now is trace what happens at the
server level
- either exception handling
- debug operation
and check what fails

Have the following message :X Error of failed request:
BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 66 (X_PolySegment)
Resource id in failed request: 0x1e0000d
Serial number of failed request: 4397
Current serial number in output stream: 4415
and some like this :

0806cab8: get_key_value() = OBJECT_NAME_NOT_FOUND
Hope that helps.


___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Sylvain Petreolle]

Post by Eric Pouech
- debug operation
and check what fails

that's what i get when i try to attach :
0831c758: debug_process( pid=0x806ba80 )
0831ce50: *attached*
0831ce50: *signal* signal=19
0831cc40: *signal* signal=19
0831ca00: *attached*
0831ca00: *signal* signal=19
0831c758: debug_process() = ACCESS_DENIED
0831c758: get_handle_fd( handle=8, access=40000000 )
0831c758: get_handle_fd() = 0 { fd=6, type=1, flags=0
}
0831c758: get_handle_fd( handle=8, access=40000000 )
0831c758: get_handle_fd() = 0 { fd=6, type=1, flags=0
}
0831c758: get_handle_fd( handle=4, access=80000000 )
0831c758: get_handle_fd() = 0 { fd=9, type=1, flags=0
}
0831ce50: *wakeup* signaled=258 cookie=0x41956e2c


___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[l***@juno.com]

Post by Sylvain Petreolle
(gdb) attach 26364
Attaching to process 26364
ptrace: Operation not permitted.

What kernel? I think I remember a problem with ptrace with early 2.4.x
kernels, but ICBW. I don't have the problem with 2.4.13.

Lawson

[Sylvain Petreolle]

I use kernel-2.4.9-21 (rpm provided by Redhat using
up2date).

Post by l***@juno.com
What kernel? I think I remember a problem with
ptrace with early 2.4.x
kernels, but ICBW. I don't have the problem with
2.4.13.
Lawson

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com