Menu
▾
▴
reactos-kernel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(64) |
Oct
(438) |
Nov
(183) |
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(132) |
May
(466) |
Jun
(366) |
Jul
(392) |
Aug
(31) |
Sep
(18) |
Oct
|
Nov
|
Dec
|
|
From: Robert K. <ro...@ko...> - 2002-07-13 19:54:48
|
Yes, it should be rewritten.. ... by just using NTDLL functions. Casper Hornstrup schrieb: >lør, 2002-07-13 kl. 20:05 skrev Robert K.: > > >>Sorry, but what is psapi? >>Seems like posix. But why have a posix layer in wine if one runs a un*x >> >> > >PSAPI = Process API. You can use it to set/query process working set >information and enumerate the running processes and a few other things. > >Casper > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >reactos-kernel mailing list >rea...@li... >https://lists.sourceforge.net/lists/listinfo/reactos-kernel > > |
|
From: David K. <kr...@mi...> - 2002-07-13 19:41:21
|
Casper: There is missing E at line 59 : ifeq ($(HOST),mingw32-windows) rsym$(EX_POSTFIX): rsym.c $(HOST_CC) $(CFLAGS) -DDOS_PATHS rsym.c -o rsym$(EXE_POSTFIX) |
|
From: Casper H. <ch...@us...> - 2002-07-13 18:42:28
|
l=F8r, 2002-07-13 kl. 20:05 skrev Robert K.: > Sorry, but what is psapi? > Seems like posix. But why have a posix layer in wine if one runs a un*x PSAPI =3D Process API. You can use it to set/query process working set information and enumerate the running processes and a few other things. Casper |
|
From: Eric K. <ek...@rz...> - 2002-07-13 18:38:50
|
"Robert K." <ro...@ko...> wrote: > Sorry, but what is psapi? > Seems like posix. But why have a posix layer in wine if one runs a un*x Psapi is not related to posix! It is a 'Process Status Helper' dll that provides documented APIs similar to the ToolhelpXxxx routines. Eric |
|
From: Robert K. <ro...@ko...> - 2002-07-13 18:03:38
|
Sorry, but what is psapi? Seems like posix. But why have a posix layer in wine if one runs a un*x Steven Edwards schrieb: >Yes there are Win9xism, Unixism and other misc >wineisms all over the Wine tree. I know of about 5 >places off of the top of my head and with grep I think >I can find 20 others. > >Because of these we cannot use wines psapi.dll. We are >really left with two options of either rewriting psapi >for reactos or rewriting for wine and helping them >implement NtQuerySystemInformation in thier ntdll. >Either way the same code is going to need to be >written so we might as well save the trouble and ask >who ever is going to work on it to license thier work >as LGPL so wine can use it too. > >Steven > >--- David Welch <we...@cw...> wrote: > > >>On Wed, Jul 10, 2002 at 08:43:42PM +0200, >>KJK::Hyperion wrote: >> >> >>>what are these two for? I've never heard them >>> >>> >>> >>Win9X rubbish IIRC. >> >> >> > > >__________________________________________________ >Do You Yahoo!? >Sign up for SBC Yahoo! Dial - First Month Free >http://sbc.yahoo.com > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Two, two, TWO treats in one. >http://thinkgeek.com/sf >_______________________________________________ >reactos-kernel mailing list >rea...@li... >https://lists.sourceforge.net/lists/listinfo/reactos-kernel > > |
|
From: Casper H. <ch...@us...> - 2002-07-13 16:08:40
|
l=F8r, 2002-07-13 kl. 16:04 skrev Royce Mitchell III: > Is there any problem with using loadros with the new symbols? It may work, but I haven't used loadros for a while. Just be sure to pass symbol files after the module they describe and don't pass symbol files before system.hiv. E.g. loadros ntoskrnl.exe hal.dll system.hiv ntoskrnl.sym hal.sym x.sys x.sym is okay. > How do you configure ReactOS for debugging? Is it the same as removing > NDEBUG from the source files? Do a "make clean". Then in the config file (reactos/config), change: DBG :=3D 0 to DBG :=3D 1 Then do a "make" and/or a "make install". Casper |
|
From: KJK::Hyperion <no...@li...> - 2002-07-13 14:29:19
|
At 14.44 13/07/2002, you wrote: >Is anybody currently maintaining the posix module? yes, it's me. Please don't expect POSIX+ to even build. I'm in the middle of porting the RedHat newlib C runtime and scrapping my half-assed attempt at one, so most of the posix module should be considered dead meat until further notice |
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 14:08:41
|
Is there any problem with using loadros with the new symbols? How do you configure ReactOS for debugging? Is it the same as removing NDEBUG from the source files? ----- Original Message ----- From: "Casper Hornstrup" <ch...@us...> To: <rea...@li...> Sent: Saturday, July 13, 2002 8:18 AM Subject: [ros-kernel] More useful stack traces > I have just committed a patch that enables ReactOS to understand .stabs > symbols (only line number, function names, and source file names though, > but this is enough to get useful stack traces when not using a > debugger). When ReactOS is configured for debugging, ReactOS will try to > load symbols for every module it loads. E.g. if ReactOS loads ndis.sys, > it will also load \SystemRoot\symbols\ndis.sym if this file exists. The > .sym files generated by ReactOS dating before today are text files. The > new .sym files are binary files extracted by the tools/rsym build > utility from the non-stripped module image. If you have old .sym text > files in your ReactOS installation, you had better remove them on your > next update or expect trouble. > > Symbol files for user-mode modules are shared across processes and > cached, so the performance degration of using the symbol files is not > significant. > > A new FreeLoader is not required, but necesarry if you want to get > useful stack traces for modules passed by FreeLoader. > > I have made a new FreeLoader snapshot available at: > > http://reactos.wox.org/download.php?id=24 > > and sources are available here: > > http://reactos.wox.org/download.php?id=25 > > Happy bug-hunting to you all ;-) > > Casper > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel > |
|
From: Casper H. <ch...@us...> - 2002-07-13 13:28:25
|
I have just committed a patch that enables ReactOS to understand .stabs symbols (only line number, function names, and source file names though, but this is enough to get useful stack traces when not using a debugger). When ReactOS is configured for debugging, ReactOS will try to load symbols for every module it loads. E.g. if ReactOS loads ndis.sys, it will also load \SystemRoot\symbols\ndis.sym if this file exists. The .sym files generated by ReactOS dating before today are text files. The new .sym files are binary files extracted by the tools/rsym build utility from the non-stripped module image. If you have old .sym text files in your ReactOS installation, you had better remove them on your next update or expect trouble. Symbol files for user-mode modules are shared across processes and cached, so the performance degration of using the symbol files is not significant. A new FreeLoader is not required, but necesarry if you want to get useful stack traces for modules passed by FreeLoader. I have made a new FreeLoader snapshot available at: http://reactos.wox.org/download.php?id=24 and sources are available here: http://reactos.wox.org/download.php?id=25 Happy bug-hunting to you all ;-) Casper |
|
From: Robert D. <od...@pn...> - 2002-07-13 12:44:05
|
Hi guys,
Is anybody currently maintaining the posix module? If so a clean checkout
from CVS
fails at the following point: (I haven't looked into it any further, about
to try os2 module)
<snip>
make -C apps/baresh
make[1]: Entering directory `F:/REACTOS/source/posix/apps/baresh'
gcc -D__SUBSYSTEM_WINDOWS__ -I../../../reactos/include -pipe
-march=i386 -c -o sh.o sh.c
windres \
--include-dir ../../../reactos/include \
--output-format coff \
sh.rc sh.coff
make[1]: *** No rule to make target `../../../reactos/dk/psx/lib/psxdll.a',
needed by `sh'. Stop.
make[1]: Leaving directory `F:/REACTOS/source/posix/apps/baresh'
make: *** [all] Error 2
|
|
From: David W. <we...@cw...> - 2002-07-13 11:30:26
|
On Fri, Jul 12, 2002 at 09:17:54PM -0500, Royce Mitchell III wrote: > Could the reason why this is not working be because it's using the stripped > hal.dll? > Yes, it should be hal.nostrip.dll, sorry. |
|
From: Eric K. <ek...@rz...> - 2002-07-13 11:17:24
|
"Royce Mitchell III" <ro...@ev...> wrote:
> Appx line 1174
>
> Was:
>
> DPRINT("waited %ld usecs for busy to clear\n", Retries * 10);
>
> Should be ( I'm guessing ):
>
> DPRINT("waited %ld usecs for busy to clear\n", RetryCount * 10);
Yes, that's a typo. I'll fix it.
Eric
|
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 02:28:22
|
OOps.... discard the other one... big typo on my part... (atapi.c:1458) AtapiSendAtapiCommand() done (atapi.c:644) SrbStatus = SRB_STATUS_PENDING (atapi.c:647) AtapiStartIo() done (atapi.c:670) AtapiInterrupt() called! (atapi.c:680) Srb: c0080450 (atapi.c:684) CommandPortBase: 170 ControlPortBase: 376 (atapi.c:687) IsAtapi == TRUE (atapi.c:1959) AtapiErrorToScsi() called (atapi.c:1985) ATAPI error: SCSI_SENSE_NOT_READY (atapi.c:2069) AtapiErrorToScsi() done (atapi.c:839) AtapiInterrupt() done! (atapi.c:670) AtapiInterrupt() called! (atapi.c:675) AtapiInterrupt(): Unexpected interrupt (atapi.c:605) AtapiStartIo() called (atapi.c:1335) AtapiSendAtapiCommand() called! (atapi.c:1362) AtapiSendAtapiCommand(): TargetId: 1 (atapi.c:1382) status=51 (atapi.c:1383) waited 0 usecs for busy to clear (atapi.c:1449) CdbSize: 12 (atapi.c:1458) AtapiSendAtapiCommand() done (atapi.c:644) SrbStatus = SRB_STATUS_PENDING (atapi.c:647) AtapiStartIo() done (atapi.c:670) AtapiInterrupt() called! (atapi.c:680) Srb: c0369d8a (atapi.c:684) CommandPortBase: 170 ControlPortBase: 376 (atapi.c:687) IsAtapi == TRUE (atapi.c:704) Read data (atapi.c:719) TransferLength: 18 (atapi.c:720) TransferSize: 18 (atapi.c:733) IsLastBlock == TRUE (atapi.c:839) AtapiInterrupt() done! (atapi.c:670) AtapiInterrupt() called! (atapi.c:675) AtapiInterrupt(): Unexpected interrupt (atapi.c:670) AtapiInterrupt() called! (atapi.c:675) AtapiInterrupt(): Unexpected interrupt Initializing system32\drivers\vfatfs.sys... Bug detected code: 0x1D Divide Error Exception: 0(0) Processor: 0 CS:EIP 8:c003ce2b <ntoskrnl.exe: 3ce2b> cr2 0 cr3 272000 Proc: c0301aa6 Pid: 1 <SYSTEM> Thrd: c03126f4 Tid: 1 DS 10 ES 10 FS 30 GS 10 EAX: ffffffff EBX: c0086750 ECX: c008c988 EDX: ffffffff EBP: c00809c0 ESI: 00200000 EDI: 00000000 EFLAGS: 00010286 kESP: c0080904 kernel stack base c007e000 ESP c0080904 Frames: <ntoskrnl.exe: 3cbdd><ntoskrnl.exe: 3cc38><ntoskrnl.exe: 2ad96><ntoskrnl .exe: 334bb><ntoskrnl.exe: aa54><ntoskrnl.exe: ab51><ntoskrnl.exe: b0f0><ntoskrn l.exe: 117c> |
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 02:23:31
|
(atapi.c:1458) AtapiSendAtapiCommand() done (atapi.c:644) SrbStatus = SRB_STATUS_PENDING (atapi.c:647) AtapiStartIo() done (atapi.c:670) AtapiInterrupt() called! (atapi.c:680) Srb: c0080450 (atapi.c:684) CommandPortBase: 170 ControlPortBase: 376 (atapi.c:687) IsAtapi == TRUE (atapi.c:1959) AtapiErrorToScsi() called (atapi.c:1985) ATAPI error: SCSI_SENSE_NOT_READY (atapi.c:2069) AtapiErrorToScsi() done (atapi.c:839) AtapiInterrupt() done! (atapi.c:670) AtapiInterrupt() called! (atapi.c:675) AtapiInterrupt(): Unexpected interrupt (atapi.c:605) AtapiStartIo() called (atapi.c:1335) AtapiSendAtapiCommand() called! (atapi.c:1362) AtapiSendAtapiCommand(): TargetId: 1 (atapi.c:1382) status=51 (atapi.c:1383) waited 0 usecs for busy to clear (atapi.c:1449) CdbSize: 12 (atapi.c:1458) AtapiSendAtapiCommand() done (atapi.c:644) SrbStatus = SRB_STATUS_PENDING (atapi.c:647) AtapiStartIo() done (atapi.c:670) AtapiInterrupt() called! (atapi.c:680) Srb: c0369d8a (atapi.c:684) CommandPortBase: 170 ControlPortBase: 376 (atapi.c:687) IsAtapi == TRUE (atapi.c:704) Read data (atapi.c:719) TransferLength: 18 (atapi.c:720) TransferSize: 18 (atapi.c:733) IsLastBlock == TRUE (atapi.c:839) AtapiInterrupt() done! (atapi.c:670) AtapiInterrupt() called! (atapi.c:675) AtapiInterrupt(): Unexpected interrupt (atapi.c:670) AtapiInterrupt() called! (atapi.c:675) AtapiInterrupt(): Unexpected interrupt Initializing system32\drivers\vfatfs.sys... Bug detected code: 0x1D Divide Error Exception: 0(0) Processor: 0 CS:EIP 8:c003ce2b <hal.dll: 3ce2b> cr2 0 cr3 272000 Proc: c0301aa6 Pid: 1 <SYSTEM> Thrd: c03126f4 Tid: 1 DS 10 ES 10 FS 30 GS 10 EAX: ffffffff EBX: c0086750 ECX: c008c988 EDX: ffffffff EBP: c00809c0 ESI: 00200000 EDI: 00000000 EFLAGS: 00010286 kESP: c0080904 kernel stack base c007e000 ESP c0080904 Frames: <ntoskrnl.exe: 3cbdd><ntoskrnl.exe: 3cc38><ntoskrnl.exe: 2ad96><ntoskrnl .exe: 334bb><ntoskrnl.exe: aa54><ntoskrnl.exe: ab51><ntoskrnl.exe: b0f0><ntoskrn l.exe: 117c> |
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 02:22:26
|
Could the reason why this is not working be because it's using the stripped hal.dll? ----- Original Message ----- From: "Royce Mitchell III" <ro...@ev...> To: <rea...@li...> Sent: Friday, July 12, 2002 7:37 AM Subject: Re: [ros-kernel] disk.sys crash ( debug results ) > C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x13f98 > fake:0 > > C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x3f98 > ??:0 > > C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0xc00e3f98 > ??:0 > > > :( > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Gadgets, caffeine, t-shirts, fun stuff. > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel > |
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 01:33:02
|
Appx line 1174
Was:
DPRINT("waited %ld usecs for busy to clear\n", Retries * 10);
Should be ( I'm guessing ):
DPRINT("waited %ld usecs for busy to clear\n", RetryCount * 10);
|
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 12:42:03
|
C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x13f98 fake:0 C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x3f98 ??:0 C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0xc00e3f98 ??:0 :( |
|
From: Eric K. <ek...@rz...> - 2002-07-12 11:56:15
|
"Royce Mitchell III" <ro...@ev...> wrote: > crash is in call to DriverObject->MajorFunction[Param->MajorFunction] > > Irpsp 0xC036B2A6 > MajorFunction 15 > DriverObject->MajorFunction[Param->MajorFunction] dcb368f4 > > I'll start trying to figure out what function this is pointing to, but > pointers would be appreciated :) That should be a call to a dispatcher routine in scsiport.sys. I'd like to know whether the ZIP drive is an ATA/IDE or an ATAPI device. Please enable debug output of lines 941 and 959 in drivers/storage/atapi/atapi.c. AFAIK, Iomega made ATA and ATAPI Zip drives. Brrrrr.... :-/ Eric |
|
From: David W. <we...@cw...> - 2002-07-12 06:59:00
|
On Thu, Jul 11, 2002 at 06:42:06PM -0700, Rex Jolliff wrote: > Looks to me like the zip drive may be reporting a sector size of 0. > One thing I ought to mention is that the trap number is no longer being reported correctly by the kernel. The place to start, as always, is to find out what routine the crash occurred in. I see from the copy of the crash report that the module was hal.dll so running addr2line --exe=/PATH/TO/REACTOS/hal/halx86/hal.dll 0x13f98 will give the line number. |
|
From: James T. <jim...@ad...> - 2002-07-12 05:34:43
|
Rex Jolliff wrote: > > At 06:48 PM 7/11/02 -0500, you wrote: > >Initializing system32\drivers\class2.sys... > > > >Initializing system32\drivers\disk.sys... > > [...] > > >(disk.c:404) DiskClassCreateDeviceObject() called > >(disk.c:533) SectorSize: 512 > > [...] > > >(disk.c:247) Vendor: 'IOMEGA ZIP 100 ' > >(disk.c:404) DiskClassCreateDeviceObject() called > >Page fault at high IRQL was 12 > >Bug detected code: 0x1D > >Divide Error Exception: 0(2) > > Looks to me like the zip drive may be reporting a sector size of 0. > > Rex Jolliff > re...@lv... > Yes, that would be normal for a ide zip drive with out a disk in it. Need to make an exception for handling drives with zero for a size. James |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 04:55:19
|
Hrmm... Could that be because there's no disk in the drive? > Looks to me like the zip drive may be reporting a sector size of 0. |
|
From: Rex J. <re...@lv...> - 2002-07-12 01:35:16
|
At 06:48 PM 7/11/02 -0500, you wrote: >Initializing system32\drivers\class2.sys... > >Initializing system32\drivers\disk.sys... [...] >(disk.c:404) DiskClassCreateDeviceObject() called >(disk.c:533) SectorSize: 512 [...] >(disk.c:247) Vendor: 'IOMEGA ZIP 100 ' >(disk.c:404) DiskClassCreateDeviceObject() called >Page fault at high IRQL was 12 >Bug detected code: 0x1D >Divide Error Exception: 0(2) Looks to me like the zip drive may be reporting a sector size of 0. Rex Jolliff re...@lv... |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 01:05:27
|
crash is in call to DriverObject->MajorFunction[Param->MajorFunction] Irpsp 0xC036B2A6 MajorFunction 15 DriverObject->MajorFunction[Param->MajorFunction] dcb368f4 I'll start trying to figure out what function this is pointing to, but pointers would be appreciated :) |
|
From: Steven E. <ste...@ya...> - 2002-07-12 00:31:09
|
Oh yeah, when I first read your emails I though you were still trying to make sure thats where the problem was. I was "multi-tasking" =) and didnt notice that you were trying to find the function that was hosed. Steven --- Royce Mitchell III <ro...@ev...> wrote: > I'm sure that would work, but wouldn't it be better > to try to find out why > it's crashing? __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 00:27:20
|
I'm sure that would work, but wouldn't it be better to try to find out why it's crashing? ----- Original Message ----- From: "Steven Edwards" <ste...@ya...> To: <rea...@li...> Sent: Thursday, July 11, 2002 7:07 PM Subject: Re: [ros-kernel] disk.sys crash ( debug results ) > Have your tried it with the zip unpluged from the ide > channel? > > > (disk.c:247) Vendor: 'IOMEGA ZIP 100 ' > > (disk.c:404) DiskClassCreateDeviceObject() called > > Page fault at high IRQL was 12 > > > __________________________________________________ > Do You Yahoo!? > Sign up for SBC Yahoo! Dial - First Month Free > http://sbc.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > PC Mods, Computing goodies, cases & more > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel > |
8 messages has been excluded from this view by a project administrator.
