Comment 0 for bug 884181

I am unable to run gdb successfully on an Oneric EC2 t1.micro 64-bit instance. The simplest case for reproducing this issue is to use "gdb /bin/true" and then the "run" command. gdb will hang and an "alignment check: 0000" from the kernel will appear in the dmesg output (full message included in the included debug info).

This only seems to happen on EC2 t1.micro 64-bit instances in my limited testing. 32-bit instances seem to be OK, along with larger 64-bit instances.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-virtual 3.0.0-12.20
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 2011-10-31 11:21 seq
 crw-rw---- 1 root audio 116, 33 2011-10-31 11:21 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Mon Oct 31 11:43:51 2011
Ec2AMI: ami-bbf539d2
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t1.micro
Ec2Kernel: aki-825ea7eb
Ec2Ramdisk: unavailable
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
ProcModules: acpiphp 24080 0 - Live 0x0000000000000000
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)