My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Older

  • Aug 21, 2009
    issue 10 (xa_linux_get_taskaddr can't work) Owner changed by bdpayne   -   There's not really enough information here to take action on this bug. Could you send me the the following files... (1) code that works properly, (2) code that fails, (3) the debug log for each of these running on your machine, (4) the version of the operating system running in domU, and (5) your xenaccess.conf file? Without these details it's basically impossible to see what is happening on your system because this function is working fine on my test system at the moment.
    Owner: bdpayne
    There's not really enough information here to take action on this bug. Could you send me the the following files... (1) code that works properly, (2) code that fails, (3) the debug log for each of these running on your machine, (4) the version of the operating system running in domU, and (5) your xenaccess.conf file? Without these details it's basically impossible to see what is happening on your system because this function is working fine on my test system at the moment.
    Owner: bdpayne
  • Aug 20, 2009
    issue 10 (xa_linux_get_taskaddr can't work) reported by hnbc...@126.com   -   I am using xenaccess-0.5 on my fedora 8. I want to use these codes to get the relavent addresses for my process: if (XA_OS_LINUX == xai.os_type){ if (xa_linux_get_taskaddr(&xai, client_pid, &taskaddr) == XA_FAILURE){ perror("failed to get task addresses"); goto error_exit; } } it can't work correctly and gives me no output. i use the function in other places just in the same procedure, and there is no error. Please give me some help!
    I am using xenaccess-0.5 on my fedora 8. I want to use these codes to get the relavent addresses for my process: if (XA_OS_LINUX == xai.os_type){ if (xa_linux_get_taskaddr(&xai, client_pid, &taskaddr) == XA_FAILURE){ perror("failed to get task addresses"); goto error_exit; } } it can't work correctly and gives me no output. i use the function in other places just in the same procedure, and there is no error. Please give me some help!
  • Aug 17, 2009
    r218 (adding new windows kernel base address ) committed by bdpayne   -   adding new windows kernel base address
    adding new windows kernel base address
  • May 29, 2009
    r217 (added check for xen 3.4.0 ) committed by bdpayne   -   added check for xen 3.4.0
    added check for xen 3.4.0
  • May 29, 2009
    r216 (added check for new xen version 3.4.0 ) committed by bdpayne   -   added check for new xen version 3.4.0
    added check for new xen version 3.4.0
  • May 20, 2009
    ConfigurationEntries (Working configuration file entries.) Wiki page edited by bdpayne
  • May 08, 2009
    r214 (fixed dependency problem with the build process ) committed by bdpayne   -   fixed dependency problem with the build process
    fixed dependency problem with the build process
  • May 07, 2009
    r213 (some additional wish list items ) committed by bdpayne   -   some additional wish list items
    some additional wish list items
  • May 07, 2009
    r212 (some future planning ) committed by bdpayne   -   some future planning
    some future planning
  • May 06, 2009
    r211 (fixing the ENABLE_XEN problem, users of XA will no longer ne...) committed by bdpayne   -   fixing the ENABLE_XEN problem, users of XA will no longer need to #define ENABLE_XEN in their code
    fixing the ENABLE_XEN problem, users of XA will no longer need to #define ENABLE_XEN in their code
  • May 06, 2009
    r210 (this use of AC_OUTPUT with arguments is deprecated, this cha...) committed by bdpayne   -   this use of AC_OUTPUT with arguments is deprecated, this change lets autoconf work in the currently recommended way
    this use of AC_OUTPUT with arguments is deprecated, this change lets autoconf work in the currently recommended way
  • May 06, 2009
    r209 (following convention of other functions, xa_access_user_va_r...) committed by bdpayne   -   following convention of other functions, xa_access_user_va_range should get the kernel cr3 value from the current context
    following convention of other functions, xa_access_user_va_range should get the kernel cr3 value from the current context
  • May 06, 2009
    r208 (removed hard coded PROT_READ for user space cache hit ) committed by bdpayne   -   removed hard coded PROT_READ for user space cache hit
    removed hard coded PROT_READ for user space cache hit
  • May 05, 2009
    r207 (fixed bug introduced by the linux user address space fix ear...) committed by bdpayne   -   fixed bug introduced by the linux user address space fix earlier today, the v2p translation needs to happen before the cache update
    fixed bug introduced by the linux user address space fix earlier today, the v2p translation needs to happen before the cache update
  • May 05, 2009
    r206 (fixed issue with accessing linux user space addresses ) committed by bdpayne   -   fixed issue with accessing linux user space addresses
    fixed issue with accessing linux user space addresses
  • May 05, 2009
    r205 (Added example filesystem that exposes Xen guest memory as a ...) committed by mooyix   -   Added example filesystem that exposes Xen guest memory as a regular file (like /dev/mem)
    Added example filesystem that exposes Xen guest memory as a regular file (like /dev/mem)
  • May 05, 2009
    issue 9 (documentation doesn't like xen-devel as a dependency) Status changed by bdpayne   -   Fixed in r204.
    Status: Fixed
    Fixed in r204.
    Status: Fixed
  • May 05, 2009
    r204 (updated documentation to include mention of xen-devel depend...) committed by bdpayne   -   updated documentation to include mention of xen-devel dependency for pre-package xen installations
    updated documentation to include mention of xen-devel dependency for pre-package xen installations
  • May 05, 2009
    issue 6 (module list example accesses string incorrectly) Status changed by bdpayne   -   Fixed in r203.
    Status: Fixed
    Fixed in r203.
    Status: Fixed
  • May 05, 2009
    r203 (updated module-list to parse _UNICODE_STRING struct properly...) committed by bdpayne   -   updated module-list to parse _UNICODE_STRING struct properly update process-list to have name offset that matches my dev machine
    updated module-list to parse _UNICODE_STRING struct properly update process-list to have name offset that matches my dev machine
  • Apr 21, 2009
    ConfigurationEntries (Working configuration file entries.) Wiki page edited by bdpayne
  • Mar 27, 2009
    issue 9 (documentation doesn't like xen-devel as a dependency) reported by bdpayne   -   Both the readme and the web documentation should list xen-devel as a dependency for users that choose to install xen from their linux distribution's packages.
    Both the readme and the web documentation should list xen-devel as a dependency for users that choose to install xen from their linux distribution's packages.
  • Mar 11, 2009
    issue 8 (xa_linux_get_taskaddr could not find task struct) Status changed by bdpayne   -   The posted indicated that this function does work in some cased. This is only actionable if we can isolate a code defect that is causing the function to fail (as opposed to a configuration issue).
    Status: Invalid
    The posted indicated that this function does work in some cased. This is only actionable if we can isolate a code defect that is causing the function to fail (as opposed to a configuration issue).
    Status: Invalid
  • Mar 11, 2009
    issue 8 (xa_linux_get_taskaddr could not find task struct) reported by hnbc...@126.com   -   I am using xenaccess-0.5 on my fedora 8. I want to use xa_linux_get_taskaddr to extracts information about the specified process' location in memory from the task struct specified by pid, but it does work and give me the output:"ERROR: could not find task struct for pid = 3363" i have another procedure which also uses the function, and there is no error. Please give me some help!
    I am using xenaccess-0.5 on my fedora 8. I want to use xa_linux_get_taskaddr to extracts information about the specified process' location in memory from the task struct specified by pid, but it does work and give me the output:"ERROR: could not find task struct for pid = 3363" i have another procedure which also uses the function, and there is no error. Please give me some help!
  • Mar 03, 2009
    r201 (fixed typo in path ) committed by mooyix   -   fixed typo in path
    fixed typo in path
  • Feb 23, 2009
    r200 (as long as we have the right cr3 value, kernel / user doesn'...) committed by bdpayne   -   as long as we have the right cr3 value, kernel / user doesn't matter for page table lookups
    as long as we have the right cr3 value, kernel / user doesn't matter for page table lookups
  • Feb 20, 2009
    r199 (Fixed incorrect multiplier when setting memory size. ) committed by mooyix   -   Fixed incorrect multiplier when setting memory size.
    Fixed incorrect multiplier when setting memory size.
  • Feb 20, 2009
    r198 (fixed bug introduced with yesterday's patch. pv domains mak...) committed by bdpayne   -   fixed bug introduced with yesterday's patch. pv domains make a distincton between machine and physical addresses, hvm do not.
    fixed bug introduced with yesterday's patch. pv domains make a distincton between machine and physical addresses, hvm do not.
  • Feb 20, 2009
    issue 7 (xa_windows_get_peb not working) Status changed by bdpayne   -   Fixed with r197.
    Status: Fixed
    Fixed with r197.
    Status: Fixed
  • Feb 19, 2009
    r197 (fixed bugs associated with accessing user memory and getting...) committed by bdpayne   -   fixed bugs associated with accessing user memory and getting peb on windows
    fixed bugs associated with accessing user memory and getting peb on windows
  • Feb 13, 2009
    r196 (useful description of the pe format ) committed by bdpayne   -   useful description of the pe format
    useful description of the pe format
  • Feb 13, 2009
    issue 7 (xa_windows_get_peb not working) reported by bdpayne   -   xa_windows_get_peb function seems to be broken. Running process-data example on winxpsp2 doesn't work.
    xa_windows_get_peb function seems to be broken. Running process-data example on winxpsp2 doesn't work.
  • Feb 13, 2009
    r195 (added pe parsing capability, now we don't need a windows sys...) committed by bdpayne   -   added pe parsing capability, now we don't need a windows sysmap file and the exports are pulled straight from memory as needed. also more robust kernel base address detection that is much faster in the worst case
    added pe parsing capability, now we don't need a windows sysmap file and the exports are pulled straight from memory as needed. also more robust kernel base address detection that is much faster in the worst case
  • Feb 12, 2009
    r194 (updated to know about xen 3.3.1 and 3.2.3 ) committed by bdpayne   -   updated to know about xen 3.3.1 and 3.2.3
    updated to know about xen 3.3.1 and 3.2.3
  • Feb 12, 2009
    issue 6 (module list example accesses string incorrectly) reported by bdpayne   -   The module list example does not properly access the string value for the name of the module on windows domains. It should go to the UNICODE_STRING type inside the structure, parse this struct, and then follow the pointer to the string. Instead, it is just jumping past the end of the struct and assuming that the string will be there (which isn't always the case).
    The module list example does not properly access the string value for the name of the module on windows domains. It should go to the UNICODE_STRING type inside the structure, parse this struct, and then follow the pointer to the string. Instead, it is just jumping past the end of the struct and assuming that the string will be there (which isn't always the case).
  • Feb 11, 2009
    CompatibleXenVersions (Status of XenAccess support for various Xen versions.) Wiki page edited by bdpayne
  • Feb 10, 2009
    r192 (minor fix in kpgd discovery for windows, should reduce the n...) committed by bdpayne   -   minor fix in kpgd discovery for windows, should reduce the number of times that this must fall back to an exaustive search
    minor fix in kpgd discovery for windows, should reduce the number of times that this must fall back to an exaustive search
  • Feb 09, 2009
    issue 5 (dump-memory broken) reported by bdpayne   -   dump memory example program doesn't actually dump all of memory. perhaps because of the 4m kernel pages? need to investigate further.
    dump memory example program doesn't actually dump all of memory. perhaps because of the 4m kernel pages? need to investigate further.
  • Jan 31, 2009
    r191 (Allows for the specification of the Windows kernel base addr...) committed by hajime.inoue   -   Allows for the specification of the Windows kernel base address, the ntoskrnl offset, in the configuration file. Previously, this was always calculated at runtime. If this is specified in the configuration file, as ntoskrnl = <OFFSET>; This calculation is now skipped. If it is not specified, the calculation proceeds as before.
    Allows for the specification of the Windows kernel base address, the ntoskrnl offset, in the configuration file. Previously, this was always calculated at runtime. If this is specified in the configuration file, as ntoskrnl = <OFFSET>; This calculation is now skipped. If it is not specified, the calculation proceeds as before.
  • Jan 25, 2009
    r190 (Changed most of the error reports to print to stderr instead...) committed by hajime.inoue   -   Changed most of the error reports to print to stderr instead of stdout.
    Changed most of the error reports to print to stderr instead of stdout.
  • Jan 25, 2009
    r189 (Changed the default parser from yacc to bison. Changed the ...) committed by hajime.inoue   -   Changed the default parser from yacc to bison. Changed the flags config/Makefile.am to use yacc flags. It's possible that if bison isn't found the flags in Makefile.am will be incorrect. Need to check this.
    Changed the default parser from yacc to bison. Changed the flags config/Makefile.am to use yacc flags. It's possible that if bison isn't found the flags in Makefile.am will be incorrect. Need to check this.
  • Jan 19, 2009
    r188 (Added XA_OS_UNKNOWN as a third OS type. ) committed by hajime.inoue   -   Added XA_OS_UNKNOWN as a third OS type.
    Added XA_OS_UNKNOWN as a third OS type.
  • Jan 05, 2009
    r187 (updated version numbers for devel line to continue ) committed by bdpayne   -   updated version numbers for devel line to continue
    updated version numbers for devel line to continue
  • Jan 05, 2009
    r186 (tagging 0.5 release ) committed by bdpayne   -   tagging 0.5 release
    tagging 0.5 release
  • Jan 05, 2009
    xenaccess-0.5.tar.gz (XenAccess 0.5 Release) file uploaded by bdpayne   -  
    Labels: Featured Type-Source
    Labels: Featured Type-Source
  • Jan 05, 2009
    r185 (updated version number in source for release ) committed by bdpayne   -   updated version number in source for release
    updated version number in source for release
  • Jan 05, 2009
    r184 (updated readme to include a note about using the volatility ...) committed by bdpayne   -   updated readme to include a note about using the volatility patch
    updated readme to include a note about using the volatility patch
  • Jan 05, 2009
    r183 (this patch allows volatility to work with pyxa ) committed by bdpayne   -   this patch allows volatility to work with pyxa
    this patch allows volatility to work with pyxa
  • Dec 19, 2008
    r182 (a few more minor issues ) committed by bdpayne   -   a few more minor issues
    a few more minor issues
  • Dec 19, 2008
    r181 (fixed off by one in version constant numbering ) committed by bdpayne   -   fixed off by one in version constant numbering
    fixed off by one in version constant numbering
 
Hosted by Google Code