[Bug 1446291] [NEW] gcc/g++ 4.8.2 won't convert uint64 to char properly.
Public bug reported:
I have an Ubuntu 14.04 system for arm7l (armhf), and I think
I have found a bug in the g++/gcc compiler.
I am expecting to see 'char c' below to end up as a negative number,
but as you can see, it does not. x86 system shows the negative number
as expected.
Anyone have any ideas for a work-around, or proper code if mine is
buggy?
greearb@build-imx6:~/git/btbits/server$ more test.cc
#include
#include
int main() {
unsigned long long val = 0x8b;
char c = val;
printf("c: %d 0x%x\n", c, c);
return 0;
}
greearb@build-imx6:~/git/btbits/server$ g++ -o test test.cc
greearb@build-imx6:~/git/btbits/server$ ./test
c: 139 0x8b
greearb@build-imx6:~/git/btbits/server$
greearb@build-imx6:~/git/btbits/server$ g++ --version
g++ (Ubuntu/Linaro 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
On x86 system:
[greearb@ben-dt ~]$ g++ -o test test.cc
[greearb@ben-dt ~]$ ./test
c: -117 0xff8b
[greearb@ben-dt ~]$ gcc --version
gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8)
** Affects: gcc-4.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446291
Title:
gcc/g++ 4.8.2 won't convert uint64 to char properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1446291/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446909] [NEW] pkill kills self when called from C program
Public bug reported: This does not happen on Fedora. Source code example pasted below. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: procps 1:3.3.9-1ubuntu2.2 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Tue Apr 21 17:13:07 2015 InstallationDate: Installed on 2014-09-22 (211 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sysctl.conf: [modified] mtime.conffile..etc.sysctl.conf: 2014-09-30T12:34:06.956063 ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "source code example shows problem" https://bugs.launchpad.net/bugs/1446909/+attachment/4380885/+files/test-pkill.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446909 Title: pkill kills self when called from C program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1446909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446909] Re: pkill kills self when called from C program
I did some extra testing on this bug today. I compiled and installed the latest procps-ng (3.3.10) on Ubuntu 14.04 i386, and it sees the problem: greearb@v-ubuntu-14-04-i386:~$ ./test-pkill System command failed: ERROR: system command "pkill -f my-funky-cmdline" terminated with signal 15 my-system rv: 15 greearb@v-ubuntu-14-04-i386:~$ pkill --version pkill from procps-ng 3.3.10 greearb@v-ubuntu-14-04-i386:~$ But, exact same procps and test-pkill code works fine on Fedora-20: [greearb@v-f20-32 ~]$ ./test-pkill System command failed: ERROR: system command "pkill -f my-funky-cmdline" had return code: 1 my-system rv: 256 [greearb@v-f20-32 ~]$ pkill --version pkill from procps-ng 3.3.10 [greearb@v-f20-32 ~]$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446909 Title: pkill kills self when called from C program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1446909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125702] Re: casper-rw fs not cleanly unmounted on persistent live USB shutdown
I built a custom 12.04 with some added kernel patches and added a few packages (and removed others). It generally seems to work fine, but at some point, I started seeing errors about /dev/loop1. It seems this is the casper-rw file, and it is not checked by fsck on startup. Why not? I put the usb stick in a different machine, manually ran fsck on the casper-rw file, and it found and fixed a bunch of errors. Now the usb key boots up fine again, but I'm worried that this will happen again... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125702 Title: casper-rw fs not cleanly unmounted on persistent live USB shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/125702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996668] [NEW] Should run fsck before mounting casper-rw
Public bug reported:
If you crash your pendrive system, casper-rw can be corrupted.
casper should check using fsck before mounting casper-rw to
catch this and allow users to fix the problem if it cannot be fixed
automatically.
Here's a patch that I think will do the trick for the ext2/3/4 file-systems
at least. I coppied e2fsck.static to the ramdisk and put it in sbin.
greearb@v-ubuntu-12-04:/tmp/ramdisk/scripts$ diff -u ~/casper.orig casper
--- /home/greearb/casper.orig 2012-05-08 09:09:43.012658969 -0700
+++ casper 2012-05-08 10:43:20.016662223 -0700
@@ -441,6 +441,14 @@
fi
fi
+if [ "_${cow_fstype}" = "_ext2" -o "_${cow_fstype}" = "_ext3" -o
"_${cow_fstype}" = "_ext4" ]
+ then
+ [ "$quiet" != "y" ] && log_warning_msg "Running e2fsck on ${cowdevice},
fstype: ${cow_fstype}"
+ e2fsck -p ${cowdevice} || panic "ERROR: File system corruption on
${cowdevice}. Run: e2fsck ${cowdevice}"
+else
+ [ "$quiet" != "y" ] && log_warning_msg "Not running fsck on
${cowdevice}, only ext2/2/4 fsck supported: ${cow_fstype}"
+fi
+
mount -t ${cow_fstype} -o ${cow_mountopt} ${cowdevice} /cow || panic "Can
not mount $cowdevice on /cow"
case ${UNIONFS} in
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996668
Title:
Should run fsck before mounting casper-rw
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/996668/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125702] Re: casper-rw fs not cleanly unmounted on persistent live USB shutdown
Maybe this will do the trick? https://bugs.launchpad.net/ubuntu/+source/casper/+bug/996668 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125702 Title: casper-rw fs not cleanly unmounted on persistent live USB shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/125702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982413] Re: unity-panel-service crashed with SIGSEGV in service_proxy_cb() when running virtual box
I re-spun a 12.04 live-cd, and it happens on bootup (almos?) every time. Dmesg shows: panel[foo]: segfault at c ip libindicator.so.7.0.0 Bug seemed to start happening after I did an apt-get dist-upgrade, as it worked fine in an earlier 12.04 respin that I did. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982413 Title: unity-panel-service crashed with SIGSEGV in service_proxy_cb() when running virtual box To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/982413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125702] Re: casper-rw fs not cleanly unmounted on persistent live USB shutdown
Well, I think I finally have this working...mainly due to lots of help from the aufs maintainer and mailing list. Will attach the /etc/init.d/umountrootfs and casper initrd scripts (for Ubuntu 12.04). You have to re-spin the live-cd initrd to get the casper changes in place. The umountrootfs just needs to be copied to /etc/init.d/umountrootfs (on the live-cd image you are re-spining). ** Attachment added: "Make /cow visible, add fsck for casper-rw." https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/125702/+attachment/3151349/+files/casper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125702 Title: casper-rw fs not cleanly unmounted on persistent live USB shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/125702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125702] Re: casper-rw fs not cleanly unmounted on persistent live USB shutdown
Well, I think I finally have this working...mainly due to lots of help from the aufs maintainer and mailing list. Will attach the /etc/init.d/umountrootfs and casper initrd scripts (for Ubuntu 12.04). You have to re-spin the live-cd initrd to get the casper changes in place. The umountrootfs just needs to be copied to /etc/init.d/umountrootfs (on the live-cd image you are re-spining). ** Attachment added: "Make /cow visible, add e2fsck for casper-rw." https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/125702/+attachment/3151350/+files/casper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125702 Title: casper-rw fs not cleanly unmounted on persistent live USB shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/125702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125702] Re: casper-rw fs not cleanly unmounted on persistent live USB shutdown
Here is the /etc/init.d/umountroot file. The main trick to properly unmounting aufs root is this: mount -n -o remount,noxino / || echo "Remount noxino / failed: $?" # This next fails, but over-all, things work, so leaving it in in case # it has some partial benefit. mount -n -o remount,mod:/cow=ro / || echo "Remount /cow(ro) failed: $?" mount -n -o remount,ro /cow || echo "Remount /cow (ro) failed: $?" mount -n -o remount,ro / ** Attachment added: "Cleanly unmount aufs / and /cow" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/125702/+attachment/3151378/+files/umountroot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125702 Title: casper-rw fs not cleanly unmounted on persistent live USB shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/125702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996668] Re: Should run fsck before mounting casper-rw
I have a better fix for this, posted here: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/125702 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996668 Title: Should run fsck before mounting casper-rw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/996668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 125702] Re: casper-rw fs not cleanly unmounted on persistent live USB shutdown
On 05/17/2012 05:20 PM, wodny wrote: > The noxino idea is not new. I've mentioned this in comment #85 almost > half a year ago. And it itself was based on an earlier comment. > > What do You mean that those 3 lines fail? Have You tried doing it in right > order, also mentioned in this thread? >/cdrom -no remount,ro >/ -no remount,noxino, >/cow -no remount,ro > It's been even tested. > > You mention the mailing list - would You provide a link to the thread? > > And is this discussion still relevant? I thought Ubuntu has switched to > overlayfs. I didn't read the whole thread..but Ubuntu 12.04 is still busted. After my changes, including noxinfo, it works for me. I hear they are moving away from aufs to overlayfs, but I guess that is post 12.04. Here's the mail archives from sourceforge: http://sourceforge.net/mailarchive/forum.php?thread_name=4FB5807D.6000307%40candelatech.com&forum_name =aufs-users Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/125702 Title: casper-rw fs not cleanly unmounted on persistent live USB shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/125702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
