On Wed, Oct 18, 2006 at 11:25:18PM +0200, Jan Dittmer wrote:
> As I wrote in the original message: Debian/etch amd64 host+guest,
> running btlaunchmany (from the bittorrent package). I can put you
> the compressed root + kernel somewhere if that helps. It's roughly
> 100mb.
Yeah, that would be use
Jeff Dike wrote:
> On Wed, Oct 18, 2006 at 09:16:14PM +0200, Jan Dittmer wrote:
>> This is 100% reproducible here. Perfect test case. How to debug?
>
> You want to dig into the code and see what's wrong? Put a breakpoint
> on the force_sig_info(SIGSEGV, ...) in segv(). Then find the faulting
> i
On Wed, Oct 18, 2006 at 09:16:14PM +0200, Jan Dittmer wrote:
> This is 100% reproducible here. Perfect test case. How to debug?
You want to dig into the code and see what's wrong? Put a breakpoint
on the force_sig_info(SIGSEGV, ...) in segv(). Then find the faulting
instruction -
RIP is
try exporting LD_ASSUME_KERNEL=2.4.1 before executing Your application,
to see if that works - this disables usage of NPTL
Jan Dittmer wrote:
> Jeff Dike wrote:
>
>> On Wed, Oct 18, 2006 at 05:33:50PM +0200, Jan Dittmer wrote:
>>
>>> clone(Process 484 attached
>>> child_stack=0x4244e280,
Jeff Dike wrote:
> On Wed, Oct 18, 2006 at 05:33:50PM +0200, Jan Dittmer wrote:
>> clone(Process 484 attached
>> child_stack=0x4244e280,
>> flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID|CLONE_DETACHED,
>>
>> par
On Wed, Oct 18, 2006 at 05:33:50PM +0200, Jan Dittmer wrote:
> clone(Process 484 attached
> child_stack=0x4244e280,
> flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID|CLONE_DETACHED,
>
> parent_tidptr=0x4244e9f0, t
- Guest 2.6.19-rc1-git11
- Host Debian 2.6.18-1-amd64
- Debian etch for host and guest
- both using ext3
- command to start the guest
./linux-2.6.19-rc1-git11 ubd0=umlblob.cow,etch-amd64.img \
eth0=daemon,10:00:00:00:00:02,unix,/var/run/uml-utilities/uml_switch.ctl \
mem=128M \
