In addition to Juan's comments:
it would be nice if, when you post new patches that obsolete old ones,
if you stated that clearly. Otherwise we have to think a bit to decide
if they apply on top of your old ones.
Paul Romanyszyn wrote:
This app is downloadable and takes only a few steps to reproduce.
Thanks for testing Paul... the app is not the culprit as the fault
occurs while loading kernel32 debug information... you should get the
same error for any app you load under winedbg (if you load kernel3
Eric Pouech wrote:
running a 16 bit application from bug Bug 5493
now gives an a continuous list of
fixme:dbghelp_dwarf:dwarf2_compute_location Unhandled attr op: 75
instead of continuous page faulting between on the lookup.
What traces do you need and I will add them to that bug.
does the
Hi Lukasz, you probably didn't notice that most patches didn't get through this
week. There were several other rather large series sent, in addition to the
usual traffic. My guess is Alexandre only had time for the easy ones this week.
Your patches looked pretty good. The only suggestion I'd
On Friday, 26. Mai 2006 Detlef Riekenberg wrote:
> Am Mittwoch, den 24.05.2006, 20:24 +0200 schrieb Stefan Leichter:
>
> > > The cross-compiled WRT failed since 17. May.
>
> > I have already send a patch to Paul, to fix the cross compiling,
>
> Many Thanks.
>
>
> > but it looks like Paul is no
Hi,
The attached patch modifies IWineD3D::CheckDeviceFormat to whitelist supported
formats and return unsupported on unknown formats. Games which use funky
float formats or simmilar things should then see that the formats aren't
supported and (hopefully) fall back to less fancy formats. Before I
Hi,
> I looked at that, and it is a reference counting issue. Red alert deals
> nicely with its surfaces and the ddraw object itself, but it creates a
> palette and doesn't release it. A palette holds a reference to the
> DirectDraw interface it was created from, this is shown by a test case I
> se
Hi,
> Command & Conquer and C&C: Red Alert
> When exiting the game, a messagebox displays: 'Unregonized Direct Draw
> result code: 1'
> A demo of Red Alert is available here:
> http://appdb.winehq.org/appview.php?versionId=4026
> These two games, along with 'Warlords : Darklords Rising' also ha
Especially i'd like to know why it hasn't been accepted. It would be
nice to have some starting point in the tree, as i've much more done but
can't send it anyway. :/
It would be a lot of work to cut the patches into smaller parts at some
point. Especially with no feedback...
--
thanks,
Łukasz Ch
Ge van Geldorp wrote:
From: Eric Pouech [mailto:[EMAIL PROTECTED]
this one is questionnable. Now that we have stackwalk64
implemented (I'm not saying it works flawlessly on 64bit
machines), it may be more interesting here to use the 64 bit
version of the call back
That's actually a se
running a 16 bit application from bug Bug 5493
now gives an a continuous list of
fixme:dbghelp_dwarf:dwarf2_compute_location Unhandled attr op: 75
instead of continuous page faulting between on the lookup.
What traces do you need and I will add them to that bug.
does the attached patch help ?
Am Freitag 30 Juni 2006 17:28 schrieb Christoph Frick:
> On Fri, Jun 30, 2006 at 05:11:24PM +0200, Alexander Nicolaysen Sørnes wrote:
> > ...
> > fixme:d3d:IWineD3DStateBlockImpl_Release Releasing primary stateblock
> >
> > ...
> > fixme:d3d:IWineD3DStateBlockImpl_Release Releasing primary stateblo
Hi,
> as this seems already solved just for the files. this fix let Planescape
> Torment crash (before it just ended silently by releasing its "primary
> state block") - it worked before the ddraw patches white fine. i will
> soon file a bugreport and provide a link to the demo.
Can you also attach
On Saturday 01 July 2006 01:01, Alexandre Julliard wrote:
> Yes, I think it should be renamed to cmd.exe, at this point it's
> supposed to be a complete replacement.
Not sure if this is the best place to bring this up, but I'm not sure
it's "ready". The problem is it runs through the terminal the
> From: Eric Pouech [mailto:[EMAIL PROTECTED]
>
> this one is questionnable. Now that we have stackwalk64
> implemented (I'm not saying it works flawlessly on 64bit
> machines), it may be more interesting here to use the 64 bit
> version of the call back
That's actually a separate issue. The
"Thomas Kho" <[EMAIL PROTECTED]> writes:
> I'm currently looking into what would be required for something like a
> symlink to wcmd.exe, but at the same time I'm wondering the historical
> reasons for choosing 'wcmd' and if it should be changed to just 'cmd'.
Yes, I think it should be renamed to
Ge van Geldorp wrote:
diff --git a/programs/winedbg/stack.c b/programs/winedbg/stack.c
index b976117..c2dec5f 100644
--- a/programs/winedbg/stack.c
+++ b/programs/winedbg/stack.c
@@ -127,9 +127,14 @@ BOOL stack_get_current_symbol(SYMBOL_INF
static BOOL CALLBACK stack_read_mem(HANDLE hProc, DWORD
17 matches
Mail list logo
