> OK, I finally got glibc to build with Roland's xattr patch. However,
> unfortunately it seems to be problematic. getfattr causes Illegal
> Instruction (core dumped).
>
> Here is a backtrace if it is of any use:
>
> #0 0x0114bb6a in syscall () from /lib/libc.so.0.3
> #1 0x01026820 in listx
This adds the missint {f,}{list,remove}xattr functions.
Not tested in the slightest.
2005-03-06 Roland McGrath <[EMAIL PROTECTED]>
* hurd/hurd/xattr.h: New file.
* hurd/xattr.c: New file.
* hurd/Makefile (routines): Add it.
* sysdeps/mach/hurd/fgetxattr.c: New f
OK, I finally got glibc to build with Roland's xattr patch. However,
unfortunately it seems to be problematic. getfattr causes Illegal
Instruction (core dumped).
Here is a backtrace if it is of any use:
#0 0x0114bb6a in syscall () from /lib/libc.so.0.3
#1 0x01026820 in listxattr (path=0xe8 ,
Your credit/debit card information must be updated
Dear eBay Member,
We recently noticed one or more attempts to log in to your eBay account from a
foreign IP address and we have reasons to believe that your account was used by
a third party without your authorization. I
[}KW~®
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTEC
Yes, kdb is documented in GNU Mach Reference. But I'm not aware of
documented precise instructions how to make good report for GNU
Mach panic, e.g. where to set breakpoints and what kdb commands to
be run for the report.
That depends on a case by case basis, like all debugging.
On Sun, Mar 06, 2005 at 01:42:27AM +0100, Alfred M. Szmidt wrote:
> Always tell us what function the EIP really is.
Probably not that helpful...
#v+
$ addr2line -fe gnumach 0x11a07e
Debugger
./kern/debug.c:102
#v-
#v+
cat -n kern/debug.c | grep -C 10 ^\ \ \ 102
92 asm("ta 0x81");
