|
From: b12 a.k.a. F. B. <b12...@ya...> - 2004-12-22 14:27:02
|
I'm trying to debug a windows application using valgrind through wine, but all my attemps failed. I first tried with valgrind 2.2.0 and I get the following error: Executable range 0x78000000-0x780023b0 is outside the acceptable range (nil)-0x57f00000 valgrind: do_exec(/usr/lib/wine/bin/wine-preloader) failed: Cannot allocate memory After some reseach on the web I found that this is a known problem and that there exists a special version of valgrind that should work. I downloaded this version (valgrind-20031012-wine.tar.bz2) and tried it. It compiled fine but I get this error when using it: symbol lookup error: /usr/local/lib/valgrind/valgrind.so: undefined symbol: __libc_accept If I understand well the problem, this version is too old to work with recent glibc. Then I tried to apply Adam Gundy's patch to the 2.2.0 source tree. But it does not apply cleanly. I get 16 rejects. Is there someone using valgrind with wine who could help me on this? ** |
|
From: Tom H. <th...@cy...> - 2004-12-22 14:37:03
|
In message <41C...@ya...>
b12...@ya... wrote:
> I'm trying to debug a windows application using valgrind through wine,
> but all my attemps failed.
>
> I first tried with valgrind 2.2.0 and I get the following error:
>
> Executable range 0x78000000-0x780023b0 is outside the
> acceptable range (nil)-0x57f00000
> valgrind: do_exec(/usr/lib/wine/bin/wine-preloader) failed: Cannot
> allocate memory
>
> After some reseach on the web I found that this is a known problem and
> that there exists a special version of valgrind that should work. I
> downloaded this version (valgrind-20031012-wine.tar.bz2) and tried
> it.
That version will probably work although you may need to start
your program using wine-pthread rather than wine to make sure that
it uses the pthread loader.
> It compiled fine but I get this error when using it:
>
> symbol lookup error: /usr/local/lib/valgrind/valgrind.so: undefined
> symbol: __libc_accept
>
> If I understand well the problem, this version is too old to work with
> recent glibc.
So long as you've built valgrind against the same glibc you are trying
to run against there shouldn't be any problem.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: b12 a.k.a. F. B. <b12...@ya...> - 2004-12-22 15:15:11
|
Tom Hughes wrote: >In message <41C...@ya...> > b12...@ya... wrote: > > > >>I'm trying to debug a windows application using valgrind through wine, >>but all my attemps failed. >> >>I first tried with valgrind 2.2.0 and I get the following error: >> >>Executable range 0x78000000-0x780023b0 is outside the >>acceptable range (nil)-0x57f00000 >>valgrind: do_exec(/usr/lib/wine/bin/wine-preloader) failed: Cannot >>allocate memory >> >>After some reseach on the web I found that this is a known problem and >>that there exists a special version of valgrind that should work. I >>downloaded this version (valgrind-20031012-wine.tar.bz2) and tried >>it. >> >> > >That version will probably work although you may need to start >your program using wine-pthread rather than wine to make sure that >it uses the pthread loader. > > That is the way I tried it. Here is the exact command line I used: valgrind --tool=helgrind --trace-children=yes wine-pthread test.exe Note that if I don't use the --trace-children=yes option, it's working fine. But I don't thing that without this option valgrind debugs something else than wine itself. Or maybe I'm wrong with this? > > >>It compiled fine but I get this error when using it: >> >>symbol lookup error: /usr/local/lib/valgrind/valgrind.so: undefined >>symbol: __libc_accept >> >>If I understand well the problem, this version is too old to work with >>recent glibc. >> >> > >So long as you've built valgrind against the same glibc you are trying >to run against there shouldn't be any problem. > > > I don't know how I could check that. I'm pretty new to Linux. But I think I only have one glibc version on my system. (I installed Linux on this computer less than one month ago, and I have not upgraded glibc since then) >Tom > > > |
|
From: Tom H. <th...@cy...> - 2004-12-22 15:58:22
|
In message <41C...@ya...>
b12...@ya... wrote:
> That is the way I tried it. Here is the exact command line I used:
>
> valgrind --tool=helgrind --trace-children=yes wine-pthread test.exe
>
> Note that if I don't use the --trace-children=yes option, it's working
> fine. But I don't thing that without this option valgrind debugs
> something else than wine itself.
> Or maybe I'm wrong with this?
We only ever used memcheck I think. I doubt helgrind will be very
useful anyway as it won't be able to see the Windows threading calls
but will instead be monitoring the pthread calls that wine itself
makes and there is little correspondence between the two.
As to --trace-children, you shouldn't need that as far as I can
recall, but I might be wrong.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: b12 a.k.a. F. B. <b12...@ya...> - 2004-12-22 16:25:08
|
Tom Hughes wrote: >In message <41C...@ya...> > b12...@ya... wrote: > > > >>That is the way I tried it. Here is the exact command line I used: >> >>valgrind --tool=helgrind --trace-children=yes wine-pthread test.exe >> >>Note that if I don't use the --trace-children=yes option, it's working >>fine. But I don't thing that without this option valgrind debugs >>something else than wine itself. >>Or maybe I'm wrong with this? >> >> > >We only ever used memcheck I think. I doubt helgrind will be very >useful anyway as it won't be able to see the Windows threading calls >but will instead be monitoring the pthread calls that wine itself >makes and there is little correspondence between the two. > > Too bad! But anyway, I have the same problem with memcheck. >As to --trace-children, you shouldn't need that as far as I can >recall, but I might be wrong. > > I will try to find out if I can debug a very simple program using memcheck without --trace-children this evening. I'll tell you... >Tom > > > Thank you for your answers. Fabrice |