This is an annoyance and not a real problem, but I'm curious if anyone has
seen this.
I have two boxes with the same versions on Mandriva 2006 and OOo 2.0.1.
I have an OOo document that uses the Nachlieli font. On my wife's box it looks
good and on mine it looks like shit. The solution was
Oleg Goldshmidt wrote:
guy keren [EMAIL PROTECTED] writes:
you'll have to forgive oleg for not understanding why you're
bothered - he probably did not mess with gentoo and with its ebuild
system.
No, I haven't. But I still don't understand what the big deal is.
Here is the memory usage on
On Fri, Mar 03, 2006 at 04:41:24PM +0200, Yosef Meller wrote:
Oleg Goldshmidt wrote:
guy keren [EMAIL PROTECTED] writes:
you'll have to forgive oleg for not understanding why you're
bothered - he probably did not mess with gentoo and with its ebuild
system.
No, I haven't. But I still
Tzafrir Cohen wrote:
On Fri, Mar 03, 2006 at 04:41:24PM +0200, Yosef Meller wrote:
Oleg Goldshmidt wrote:
guy keren [EMAIL PROTECTED] writes:
you'll have to forgive oleg for not understanding why you're
bothered - he probably did not mess with gentoo and with its ebuild
system.
No, I
Hi all!
1. Save the script that is attached to this message.
2. **As root**, run it in an empty directory.
3. As an under-privileged user, enter this directory and type ./prog.
Result: the program segfaults before printing the Msg2. My question is -
why? I should note that running the same
On Fri, 3 Mar 2006, Shlomi Fish wrote:
Hi all!
1. Save the script that is attached to this message.
2. **As root**, run it in an empty directory.
3. As an under-privileged user, enter this directory and type ./prog.
Result: the program segfaults before printing the Msg2. My question is
Shlomi Fish wrote:
Hi all!
1. Save the script that is attached to this message.
2. **As root**, run it in an empty directory.
3. As an under-privileged user, enter this directory and type ./prog.
Result: the program segfaults before printing the Msg2. My question is -
why? I should
On Saturday 04 March 2006 19:40, guy keren wrote:
On Fri, 3 Mar 2006, Shlomi Fish wrote:
Hi all!
1. Save the script that is attached to this message.
2. **As root**, run it in an empty directory.
3. As an under-privileged user, enter this directory and type ./prog.
Result: the
On Friday 03 March 2006 20:36, Baruch Even wrote:
Shlomi Fish wrote:
Hi all!
1. Save the script that is attached to this message.
2. **As root**, run it in an empty directory.
3. As an under-privileged user, enter this directory and type ./prog.
Result: the program segfaults
Shlomi Fish wrote:
On Friday 03 March 2006 20:36, Baruch Even wrote:
The thing to try would be strace and/or gdb to debug the program and see
where it crashes or enable coredumps and gdb the resulting coredump.
The problem is that when running under strace or gdb the program does not
Today, after few days, I upgraded the Debian Testing (Etch) installation
on ThinkPad R40e laptop to have the most recent package versions.
The laptop has few kernels - among them I have 2.6.15-1, 2.6.12-1 and
2.6.8-2.
The 2.6.15-1 never worked for me, when I try to boot it, it locks up
sometime
Baruch Even wrote:
That's why I also added the coredump option, increase the coredump limit
to unlimited and you'll get a coredump which is a memory dump of the
process that gdb can use to look at the state of the program during the
crash.
Baruch
It's a root suid program that is run as
On Fri, Mar 03, 2006 at 07:00:23PM +0200, Shlomi Fish wrote:
Hi all!
1. Save the script that is attached to this message.
2. **As root**, run it in an empty directory.
3. As an under-privileged user, enter this directory and type ./prog.
Result: the program segfaults before printing
Hi,
On my previous laptop, I would compile the kernel once, and then if I need to
compile the same kernel again (lets say I only changed something from being
compiled-in to being a module) I would run make, and watch it skip the
already-compiled parts quite quickly.
That way, recompiling an
14 matches
Mail list logo
