Ge van Geldorp wrote:
> Yup, using Insight (the cygwin GUI for gdb), which connects
> over a null
> modem to the GDB stub in ntoskrnl. I'm using a
> slightly-modified version,
> since the official one insists that when doing a stack
> backtrace the frame
> pointer should increase for each stack frame (which is
> correct generally but
> breaks when you're backtracing from the kernelmode stack back into the
> usermode stack). Also the official version has a problem with hardware
> watchpoints.
I use the Win32 port which comes as an add-on package with DevCpp.
However I've recently switched my pen drive compiler from DevCpp to
Code::Blocks
I'm finding the Code::Blocks built in debugger (which also uses mingw gdb)
to be excellent and have started using that in place of Insight, as it
doesn't seem have any of the problems Insight has.
In fact, I'm so impressed with Code::Blocks as a whole, I think it makes
DevCpp obsolete and needs a backend writing for rbuild. It's certainly the
best mingw enabled development tool for ROS I've come across. ;)
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
jimtabor(a)svn.reactos.org wrote:
> Clean up and fixed NtUserGetMenuItemRect. Needs more testing. I watch mplayerc swip all the menu items with out crashing.
>
>
> Updated files:
> trunk/reactos/subsys/win32k/ntuser/menu.c
>
*out
Hi,
it seems, some people have problems to install reactos from the boot cd.
The reason is, all newer pc with a P4-HT or an AMD64X2 cpu are
multiprocessor compliant. In this case, the auto choice is
multiprocessor for the computer type. If the choice isn't changed, the
multiprocessor hal and the uniprocessor kernel are installed. The next
boot will show an empty colored (light green or red) screen after
freeldr has started reactos. I think, we should disable the auto choice
for the computer type.
- Hartmut
Thomas Weidenmueller wrote:
> Murphy, Ged (Bolton) wrote:
> > which, IIRC (I don't have a compiler to hand) would throw
> up 'assignment in
> > expression' errors with our MSVC /w4 setting. We would
> therefore need
> > something like :
>
> Then don't use that warning level if it rejects good code that's not
> even confusing.
It's set via rbuilds MSDN backend. It needs functionality to set different
warning levels for different components. e.g. /w4 for core components only.
Having to do it manually is far too much effort for your average programmer
;)
Maybe I should stop moaning and correct it .... hmmm :p
> > Which has suddenly become rather long for a normally simple
> message loop
> > routine ..... LOL
>
> It's exactly the same, just ugly IMO.
I know, as I said, it was just for fun.
First day back at work after the Christmas break is hard going ;)
(and why are these mails being sent to both ros-diff and ros-dev when only
addressed to ros-dev, Gé ?)
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi GreatLord!
greatlrd(a)svn.reactos.org wrote:
> forget remove a calc value in the for loop it can do outside the loop.
>
>
>
> Updated files:
> trunk/reactos/subsys/win32k/dib/dib16bpp.c
>
I'm getting this even after a make clean,
[CC] subsys/win32k/dib/dib16bpp.c
subsys/win32k/dib/dib16bpp.c: In function `CheckClipRegion':
subsys/win32k/dib/dib16bpp.c:631: error: structure has no member named `Height'
make[1]: *** [obj-i386/subsys/win32k/dib/dib16bpp.o] Error 1
Thanks,
James
I think our problem is because we are using GAS and NASM to assemble
the various assembly files. Oughtn't we standardise on NASM? Why not?
--
http://www.munted.org.uk
Anyone that thinks an imaginary deity is going to protect them against
earthquakes and hurricanes needs psychiatric help.
This should really be
while( GetMessage( &msg, NULL, 0, 0 ) > 0 )
as GetMessage returns <0 on failure.
It will then break on failure or WM_QUIT
Just being anal though as GetMessage should never really fail ;)
-----Original Message-----
From: mbosma(a)svn.reactos.org [mailto:mbosma@svn.reactos.org]
Sent: 03 January 2006 11:50
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [mbosma] 20543: fix typos.
+ while(GetMessage(&msg,NULL,0,0))
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Thomas Weidenmueller wrote
> Murphy, Ged (Bolton) wrote:
> > This should really be
> >
> > while( GetMessage( &msg, NULL, 0, 0 ) > 0 )
> >
> > as GetMessage returns <0 on failure.
> > It will then break on failure or WM_QUIT
> >
> > Just being anal though as GetMessage should never really fail ;)
>
> See
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/winui/WinUI/WindowsUserInterface/Windowing/MessagesandMessa
> geQueues/MessagesandMessageQueuesReference/MessagesandMessageQ
> ueuesFunctions/GetMessage.asp
>
> The loop shouldn't be broken if GetMessage returns -1.
>
> - Thomas
True, I suppose it depends on the reasoning behind the GetMessage error.
MSDN does have this to say:
"Warning
Because the return value can be nonzero, zero, or -1, avoid code like this:
while (GetMessage( lpMsg, hWnd, 0, 0)) ..."
For a bit of light hearted fun, here is the MSDN suggestion:
while( (bRet = GetMessage( &msg, NULL, 0, 0 )) != 0)
{
if (bRet == -1)
{
// handle the error and possibly exit
}
else
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
}
which, IIRC (I don't have a compiler to hand) would throw up 'assignment in
expression' errors with our MSVC /w4 setting. We would therefore need
something like :
bRet = GetMessage( &msg, NULL, 0, 0 );
while( bRet != 0 )
{
if (bRet == -1)
{
// handle the error and possibly exit
}
else
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
bRet = GetMessage( &msg, NULL, 0, 0 );
}
Which has suddenly become rather long for a normally simple message loop
routine ..... LOL
A nice case for a #pragma warning() ..... or reduce the warning level for
non core components (ping)
Ged
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
hbirr(a)svn.reactos.org wrote:
>Simplified the definition of the interrupt handlers for non smp machines.
>
>
>
>Updated files:
>trunk/reactos/ntoskrnl/ke/i386/irqhand.s
>
>
>
>
GMTA :)
Best regards,
Alex Ionescu