tkreuzer(a)svn.reactos.org wrote:
> LD is stupid and doesn't handle stdcall decoration as proper as
> dlltool does (after we provided a patch) [...]
Wouldn't it have been easier to just provide a similar patch for LD
then? It was a matter of changing a strchr() call to strrchr()...
(http://sourceware.org/bugzilla/show_bug.cgi?id=9766)
We can always use a patched binutils version in the next RosBE if the
patch is not applied to the upstream source in time.
Cheers,
Colin
Hi,
> Author: cgutman
> Date: Tue Dec 21 04:35:12 2010
> New Revision: 50077
>
> URL: http://svn.reactos.org/svn/reactos?rev=50077&view=rev
> Log:
> [USBDRIVER]
> - Fix a bug that resulted in us only copying half of the old keyboard data
> - CID 10402
>
> Modified:
> trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c
>
> Modified: trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/usb/nt4compat/usbd…
> ==============================================================================
> --- trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c [iso-8859-1] Tue Dec 21 04:35:12 2010
> @@ -277,7 +277,7 @@
> }
>
> // Save old keyboard data
> - RtlCopyMemory(pdev_ext->kbd_old, data, sizeof(data));
> + RtlCopyMemory(pdev_ext->kbd_old, data, 8);
>
> // resubmit the urb
> status = usb_submit_urb(pdev_ext->dev_mgr, purb);
This change is really dangerous and should be changed to a correct fix. Using magic values on memory copying is a bad idea. Using magic values (in general) is a bad idea.
Please provide a better fix without magic value.
Regards,
P. Schweitzer
I have a doubt:
==============================================================================
--- trunk/reactos/ntoskrnl/mm/ARM3/virtual.c [iso-8859-1] (original)
+++ trunk/reactos/ntoskrnl/mm/ARM3/virtual.c [iso-8859-1] Wed Dec 22 21:59:27 2010
@@ -2446,6 +2446,9 @@
/* Check if this VAD is too high */
if (BaseVpn < Vad->StartingVpn)
{
+ /* Stop if there is no left child */
+ if (!Vad->LeftChild) break;
+
/* Search on the left next */
Vad = Vad->LeftChild;
}
@@ -2453,6 +2456,11 @@
{
/* Then this VAD is too low, keep searching on the right */
ASSERT(BaseVpn > Vad->EndingVpn);
+
+ /* Stop if there is no right child */
+ if (!Vad->LeftChild) break;
+
+ /* Search on the right next */
Vad = Vad->RightChild;
}
}========================================================
Look these lines:
+ /* Stop if there is no left child */
+ if (!Vad->LeftChild) break;
+ /* Stop if there is no right child */
+ if (!Vad->LeftChild) break;
1) Is there a typo in the copy-pasta condition?
2) Is the comment wrong or misleading?
3) Am I a complete noob?
I think the order is 3), 1), 2)
One of the latest changes has made ReactOS totally uninstallable(12 tries /12 fails) using less than 192MB Ram.It halts in first stage during copying files.
Merry Christmas!!
Hi!
I guess once long tyme ago, there was a little file called dos.h!
Need this #define _A_VOLID 0x08 /* Volume ID file */
VolumeLabelDirEntry.Fat.Attrib = 0x08;
}
I'm not able to get the wubble simulation working for the ua-ros-pkg at:
http://code.google.com/p/ua-ros-pkg
[Note: I'm a new comer to ROS]
Summary of Issue:
I am using the Q&A Format provided by the site above.
a. What steps will reproduce the problem?
1. Follow http://code.google.com/p/ua-ros-pkg/wiki/DeveloperInstall to
install uav-ros-pkg packages
2. Run roslaunch wubble_mapping simulation.launch
b. What is the expected output? What do you see instead?
Expected output: Runs as given in
http://code.google.com/p/ua-ros-pkg/wiki/ClassInstructions.
Observed output:
--------------
while processing
/opt/ros/cturtle/stacks/ua-ros-pkg-read-only/arrg/wubble_world/wubble_environments/launch/empty_blocks_world.launch:
while processing
/opt/ros/cturtle/stacks/ua-ros-pkg-read-only/arrg/wubble_world/wubble_environments/launch/world_common.launch:
Invalid roslaunch XML syntax: [Errno 2] No such file or directory:
u'/opt/ros/cturtle/stacks/ua-ros-pkg-read-only/arrg/wubble_world/wubble_environments/launch/world_common.launch'
------------
c. What version of the product are you using? On what operating system?
Latest trunk, on Ubuntu 10.04 /Lucid.
d. Additional Notes?
world_common isn't there in the given files, and neither does it get
generated during the build. Also, while running make-all.sh I get 'Built 46
packages with 1 failure'. My gearbox
has the following issue during the build:
==========================
mkdir -p build/gearbox-svn/build
cd `rospack find gearbox` && patch -d
build/gearbox-svn/src/hokuyo_aist/python --verbose < `rospack find
gearbox`/aist_python_mt.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- CMakeLists.txt 2010-11-05 17:13:52.719057243 -0700
|+++ CMakeLists.txt.ros 2010-11-05 17:12:30.921672551 -0700
--------------------------
Patching file CMakeLists.txt using Plan A...
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
Hunk #1 ignored at 41.
1 out of 1 hunk ignored -- saving rejects to file CMakeLists.txt.rej
done
===========================
I wonder whether this is causing the problem, and am not totally clear as to
how to correct this.
Thanks!
--
Ganesh
$ g++ file.c -fblocks -Wall /usr/lib/bundle1.o -arch x86_64 -o file.out
pschweitzer(a)svn.reactos.org wrote:
>
> ASSERT(Name->Length);
> ASSERT(Expression->Length);
> ASSERT(!FsRtlDoesDbcsContainWildCards(Name));
It'd be preferable to wrap that last ASSERT so it isn't compiled into release builds.
Adding functions into asserts adds overhead on release builds as they're called for no reason.
Ged.
Hello all,
I'm currently developing two project tools which are going to be used by
the German ReactOS foundation (custom IRC Server and plugin for Jameica
- http://www.willuhn.de/products/jameica/).
They shall be committed into a public ReactOS SVN repository.
Since I believe that these tools are hardly useful for the average
ReactOS developer, I don't want to commit them to our current
/trunk/tools directory in the "reactos" repository. Among other
disadvantages, every commit to them would trigger a useless BuildBot
build, source checkouts would include unnecessary stuff, etc.
As this is generally the case with most of the stuff in /trunk/tools,
I'd like to move everything below this directory and the /irc directory
into a new repository called "project-tools".
We have already done a similar step in the past for the former "web"
directory.
Additionally, the "press-media" directory would be a similar candidate
for an own "press-media" repository. After these steps, our "reactos"
repository would finally contain only OS development related stuff.
For comparison, Wine already keeps its main repository free from
unrelated stuff and has several similar repositories (see
http://source.winehq.org/git/).
If there are no objections to my idea within the next two weeks, I will
proceed and set up "project-tools" and "press-media" repositories
(preserving as much SVN history as possible).
Cheers,
Colin