[Bug 1237390] Re: stap fails with 3.5/3.8 kernels in precise
Chris, thank you! A few comments: 1) I don't know if I have advertised this already but if you care about systemtap in ubuntu I could really use some help. See https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1144040 2) If new kernels are uploaded to old ubuntu releases would it be possible to also upload new systemtap releases there? Backporting will fix some issues but sometimes new kernels come with fully new features that an old systemtap won't be able to use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237390 Title: stap fails with 3.5/3.8 kernels in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1237390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237390] Re: stap fails with 3.5/3.8 kernel in precise
I would have backported these but I did not know that it was possible to upload new packages to precise since it has already been released. Can you maybe handle such backports in the future or give some guidance? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237390 Title: stap fails with 3.5/3.8 kernel in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1237390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 953892] Re: Fails to run as unprivileged user
This might be debian bug #706817 that was fixed in systemtap 1.7-1+deb7u1. To confirm, please paste the output of ls -ld /sys/kernel/debug Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953892 Title: Fails to run as unprivileged user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/953892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203590] Re: [MIR] systemtap
I'd also like to understand the motivation behind this but meanwhile you should note that most of the security vulnerabilities can only be exploited by users that have been added to the privileged stapusr group. Just installing the package does not make you vulnerable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203590 Title: [MIR] systemtap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1203590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203590] Re: [MIR] systemtap
Is that for use with lttng user space tracepoints? Do they need CONFIG_UPROBES? (See http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=691167 ) ** Bug watch added: Debian Bug tracker #691167 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203590 Title: [MIR] systemtap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1203590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824105] Re: systemtap does not work out of the box on natty
Michael, thanks for triaging systemtap bugs. I'd really appreciate if
somebody could triage these Ubuntu specific usability issues which I
don't hit since I mostly use Debian. (See also
https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1144040 )
Regarding this particular bug, systemtap 2.1-1~experimental1 added a
patch where any failure of 'stap' will point the user directly to
README.Debian:
$ stap -v -e 'FOO'
parse error: expected 'probe', 'global', 'function', or '%{'
saw: identifier 'FOO' at input:1:1
source: FOO
^
1 parse error.
Pass 1: parsed user script and 91 library script(s) using
92232virt/25348res/2608shr/23300data kb, in 100usr/20sys/120real ms.
Pass 1: parse failed. [man error::pass1]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
Do you think this is prominent enough for users to notice?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824105
Title:
systemtap does not work out of the box on natty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/824105/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
** Attachment added: drizzle_7.1.36-stable-1ubuntu1.dsc.build https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+attachment/3567122/+files/drizzle_7.1.36-stable-1ubuntu1.dsc.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: [FFe] Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
The packages http://archive.ubuntu.com/ubuntu/pool/universe/d/drizzle/drizzle_7.1.36-stable-1ubuntu1.dsc http://archive.ubuntu.com/ubuntu/pool/universe/g/gearmand/gearmand_0.33-2.dsc http://archive.ubuntu.com/ubuntu/pool/universe/libg/libguestfs/libguestfs_1.18.10-1ubuntu2.dsc http://archive.ubuntu.com/ubuntu/pool/universe/u/ust/ust_2.1.1-1.dsc seem to build just fine with the new systemtap-sdt-dev. I'll attach build logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: [FFe] Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
** Attachment added: gearmand_0.33-2.dsc.build https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+attachment/3567123/+files/gearmand_0.33-2.dsc.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: [FFe] Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
** Attachment added: libguestfs_1.18.10-1ubuntu2.dsc.build https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+attachment/3567124/+files/libguestfs_1.18.10-1ubuntu2.dsc.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: [FFe] Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
** Attachment added: ust_2.1.1-1.dsc.build https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+attachment/3567125/+files/ust_2.1.1-1.dsc.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: [FFe] Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106957] Re: Systemtap should require kernel debug information
systemtap 2.1-1~experimental1 in debian now instructs users to see README.Debian every time stap fails. README.Debian then asks them to run the stap-prep command that installs all the required headers and debugging symbols. This has been tested on both Debian and Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/106957 Title: Systemtap should require kernel debug information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/106957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
If I compare the binary packages systemtap-sdt-dev_1.7-1_amd64.deb and
systemtap-sdt-dev_2.1-1~experimental1_amd64.deb I see that the changes
are minimal:
diff -Nur ./systemtap-sdt-dev_1.7-1_amd64.deb.unpack/usr/bin/dtrace
./systemtap-sdt-dev_2.1-1~experimental1_amd64.deb.unpack/usr/bin/dtrace
--- ./systemtap-sdt-dev_1.7-1_amd64.deb.unpack/usr/bin/dtrace 2012-03-14
14:54:16.0 +0200
+++ ./systemtap-sdt-dev_2.1-1~experimental1_amd64.deb.unpack/usr/bin/dtrace
2013-03-07 18:35:49.0 +0200
@@ -267,7 +267,9 @@
(d,fn) = mkstemp(suffix=.c)
f = open(fn,mode='w')
-f.write(static __dtrace () {}\n)
+# dummy declaration just to make the object file non-empty
+f.write(static void __dtrace (void) __attribute__((unused));\n)
+f.write(static void __dtrace (void) {}\n)
f.write(\n#include sys/sdt.h\n\n)
providers.semaphore_def_write(f)
f.close()
diff -Nur ./systemtap-sdt-dev_1.7-1_amd64.deb.unpack/usr/include/sys/sdt.h
./systemtap-sdt-dev_2.1-1~experimental1_amd64.deb.unpack/usr/include/sys/sdt.h
--- ./systemtap-sdt-dev_1.7-1_amd64.deb.unpack/usr/include/sys/sdt.h
2012-03-14 14:54:18.0 +0200
+++
./systemtap-sdt-dev_2.1-1~experimental1_amd64.deb.unpack/usr/include/sys/sdt.h
2013-03-07 18:35:51.0 +0200
@@ -130,7 +130,7 @@
(!__extension__ \
(__builtin_constant_p unsigned long long) \
(_SDT_ARGINTTYPE (x)) __sdt_unsp) \
- (1ULL (sizeof (unsigned long long) \
+ ((unsigned long long)1 (sizeof (unsigned long
long) \
* __CHAR_BIT__ - 1))) == 0) \
|| (_SDT_ARGINTTYPE (x)) -1 (_SDT_ARGINTTYPE (x)) 0))
# define _SDT_ARGSIZE(x) \
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1130626
Title:
[FFe] Update Ringtail SystemTap to 2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: [FFe] Update Ringtail SystemTap to 2.1
These changes correspond to the following upstream git commits: commit d85f7afdbff8b6056ef5221575f6fa6c59b07533 Author: Frank Ch. Eigler f...@redhat.com Date: Fri Aug 10 13:56:36 2012 -0400 PR14452: drop 1ULL literal from sys/sdt.h Use (unsigned long long) 1 instead, which is for some reason kosherer. commit 69607fca94ea279881df9d8ebc0522793b4d60e2 Author: Frank Ch. Eigler f...@redhat.com Date: Tue Jan 22 16:03:45 2013 -0500 BZ902739: make dtrace emit slightly cleaner C code When generating stub .c files, make sure that the dummy __dtrace() function is fully -Wall -Wextra -pedantic - clean by adding some decorations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: [FFe] Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1144040] [NEW] systemtap co-maintainer/tester for ubuntu wanted
Public bug reported: Hi, I'm one of the people who maintain systemtap in Debian. I care about Ubuntu a bit but I don't use Ubuntu almost anywhere so I don't tend to use systemtap on Ubuntu either. Since systemtap heavily depends on kernel versions this means that I often can't reproduce the bugs on Debian. In Debian we have RFH (request for help) bugs that can be used to recruit new people to work on a package. I don't know what the practices in Ubuntu are but if you are interested in systemtap on Ubuntu and have some extra time could you consider helping us out? Simply triaging bugs and testing new systemtap versions on Ubuntu would go a long way. This is also a good opportunity to learn about Debian packaging and/or kernel debugging. regards, Timo Lindfors lindi- on ircnet, freenode, oftc timo.lindf...@iki.fi ** Affects: systemtap (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/1144040 Title: systemtap co-maintainer/tester for ubuntu wanted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1144040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130626] Re: Update Ringtail SystemTap to 2.1
This is issue is also tracked in http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=690404 ** Bug watch added: Debian Bug tracker #690404 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690404 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130626 Title: Update Ringtail SystemTap to 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1130626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054274] Re: stap fails with error: ‘cpu_possible_map’ undeclared in function ‘_stp_stat_get’
It would be nice if the changelog entry would identify the exact kernel version that is affected by the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054274 Title: stap fails with error: ‘cpu_possible_map’ undeclared in function ‘_stp_stat_get’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1054274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034304] [NEW] /lib/udev/udev-configure-printer enumerate gets stuck on upgrade
Public bug reported:
This occured on upgrade but can be reproduced by simply stopping and
starting cups:
Steps to reproduce:
1) sudo stop cups
2) sudo start cups
Expected results:
2) system is idle
Actual results:
2) udev-configure-printer process is using a lot of CPU time and does not seem
to be exiting any time soon:
$ ps -eopid,%cpu,cmd | grep udev-configure-printe[r]
22802 33.5 /lib/udev/udev-configure-printer enumerate
More info:
1) gdb shows:
(gdb) thread apply all bt full
Thread 1 (Thread 0xb703b700 (LWP 22802)):
#0 0xb7744424 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb750f3f1 in recv () from /lib/i386-linux-gnu/libc.so.6
No symbol table info available.
#2 0xb76f82ad in _httpReadGNUTLS () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#3 0xb7333c5b in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.26
No symbol table info available.
#4 0xb733457a in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.26
No symbol table info available.
#5 0xb73308ef in _gnutls_recv_int () from
/usr/lib/i386-linux-gnu/libgnutls.so.26
No symbol table info available.
#6 0xb73394a4 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.26
No symbol table info available.
#7 0xb7339917 in ?? () from /usr/lib/i386-linux-gnu/libgnutls.so.26
No symbol table info available.
#8 0xb733b2ad in gnutls_handshake () from
/usr/lib/i386-linux-gnu/libgnutls.so.26
No symbol table info available.
#9 0xb76f6c1e in ?? () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#10 0xb76f87a8 in _httpUpdate () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#11 0xb76f88ec in httpUpdate () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#12 0xb76f9ce0 in ?? () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#13 0xb77136f0 in cupsSendRequest () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#14 0xb7713b08 in cupsDoIORequest () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#15 0xb7713e1b in cupsDoRequest () from /usr/lib/i386-linux-gnu/libcups.so.2
No symbol table info available.
#16 0x0804b97c in cupsDoRequestOrDie (resource=0x804d05e /,
request=0x8d92350, http=0x8d92668) at udev/udev-configure-printer.c:765
answer = optimized out
#17 find_matching_device_uris (map=0x8d7e938, devpath=0x8d772e0
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.4, uris=0xbfd4bd44,
usbserial=0xbfd4cd64 10071519222388, id=0xbfd4bd24) at
udev/udev-configure-printer.c:842
request = 0x8d92350
answer = 0x0
uris_noserial = {n_uris = 0, uri = 0x0}
i = optimized out
exclude_schemes = {0x804cf9c beh, 0x804cfa0 cups-pdf, 0x804cfa9
bluetooth, 0x804cfb3 dnssd, 0x804cfb9 http, 0x804cfbe https,
0x804cfc4 ipp, 0x804cfc8 lpd, 0x804cfcc ncp, 0x804cfd0
parallel, 0x804cfd9 scsi, 0x804cfde smb, 0x804cfe2 snmp, 0x804cfe7
socket}
cups = 0x8d92668
attr = optimized out
all_uris = {n_uris = 0, uri = 0x0}
n = optimized out
#18 do_add (cmd=0xbfd4ef3a /lib/udev/udev-configure-printer,
devpath=0x8d7704c
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/usb/lp1,
detach=optimized out)
at udev/udev-configure-printer.c:1430
pid = optimized out
f = 148448080
id = {full_device_id = 0x8d814e0 MFG:DYMO;CMD: ;MDL:LabelWriter
450;CLASS:PRINTER;DESCRIPTION:DYMO LabelWriter 450;SERN:10071519222388;,
mfg = 0x8d815c0 DYMO, mdl = 0x8d815d0 LabelWriter 450, sern =
0x8d815e8 10071519222388}
device_uris = {n_uris = 0, uri = 0x0}
map = 0x8d7e938
usb_device_devpath = 0x8d772e0
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.4
usbserial = 10071519222388, '\000' repeats 241 times
usblpdev = 1\000\000\000\000\000\000
is_bluetooth = 0
#19 0x080498b7 in do_enumerate (argv0=0xbfd4ef3a
/lib/udev/udev-configure-printer) at udev/udev-configure-printer.c:1661
k = optimized out
p = optimized out
d = 0x8d776b8
udev = 0x8d768a8
e = 0x8d76938
item = 0x8d7efb0
first = optimized out
r = optimized out
#20 main (argc=2, argv=0xbfd4cf84) at udev/udev-configure-printer.c:1704
add = optimized out
enumerate = optimized out
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: system-config-printer-udev 1.3.8+20120201-0ubuntu8.1
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
Uname: Linux 3.2.0-27-generic-pae i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Wed Aug 8 11:43:22 2012
ExecutablePath: /lib/udev/udev-configure-printer
MachineType: FUJITSU ESPRIMO E900
Papersize: a4
PpdFiles:
kyykky: HP Deskjet f300 Series, hpcups 3.12.2
lw450-amn: Dymo Label Printer
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae
[Bug 1034304] Re: /lib/udev/udev-configure-printer enumerate gets stuck on upgrade
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034304 Title: /lib/udev/udev-configure-printer enumerate gets stuck on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1034304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824105] Re: systemtap does not work out of the box on natty
README.Debian describes how you can install the debug symbols. I don't know how this could be automated. You can have more than one kernel installed and only want debug symbols for one kernel. If the documentation does not help you, consider running http://lindi.iki.fi/lindi/systemtap/diagnose-error-cases.bash and reporting its full output here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824105 Title: systemtap does not work out of the box on natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/824105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
Closing as INVALID since in comment #14 and #15 we agreed that the bug is not in systemtap. ** Changed in: systemtap (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000268] Re: please consider letting non-admins create ubuntu installation USB stick
Sorry to ask again but is there some specific area of code that you'd like to be reviewed more carefully? I think I found at least a few security bugs. For example it does not check that the file that the user wants to write to the USB stick is actually something that the user can normally access. This means you can tell it to write /etc/shadow to your USB stick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000268 Title: please consider letting non-admins create ubuntu installation USB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1000268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669641] Re: systemtap fails to discover installed debug modules
Thank you for triaging this. Do I understand it correctly that you are going to fix this in the kernel package and I don't need to change anything in systemtap packaging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669641 Title: systemtap fails to discover installed debug modules To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-ubuntu/+bug/669641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000268] [NEW] please consider letting non-admins create ubuntu installation USB stick
Public bug reported: This is a wishlist bug. Currently http://www.ubuntu.com/download nicely describes how a user can create Ubuntu installation USB stick using usb-creator. What it does not mention is that you need to be an admin to create the USB stick since /usr/share/polkit-1/actions/com.ubuntu.usbcreator.policy has auth_admin_keep set. This is unfortunate since it means that users can not create Ubuntu installation USB sticks on computers where they do not have admin privileges (think university class rooms, libraries, work places where people are not given root privileges to their desktops). Please consider if this could be relaxed to at least to allow local users to create such installation media. ** Affects: usb-creator (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/1000268 Title: please consider letting non-admins create ubuntu installation USB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1000268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000268] Re: please consider letting non-admins create ubuntu installation USB stick
The code at least tries to check if the drive is marked as device-is- system-internal by udisks and aborts if that is the case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000268 Title: please consider letting non-admins create ubuntu installation USB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1000268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
Ok so it indeed still shows 3.2.0-24.37 for the us.archive.ubuntu.com mirror. Unfortunately I have no idea why :( Anyways, this is definitely not a bug in systemtap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
I'm trying to improve the error messages. Can you please tell me what the output of http://lindi.iki.fi/lindi/systemtap/diagnose-error-cases.bash is on your system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
You have upgraded your kernel but not yet rebooted to this new version. Just reboot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
3.2.0-24 is not the full version number. You can see the version number of your linux packages using e.g. dpkg -l | grep linux-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
ftp://ftp.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-3.2.0-24 -generic-pae_3.2.0-24.38_i386.deb ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
Are you sure you did aptitude update? Which mirror are you using? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996364] Re: systemtap reports error 'Build-id mismatch'
Can you try apt-cache policy linux-image-3.2.0-24-generic-pae ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996364 Title: systemtap reports error 'Build-id mismatch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/996364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922860] Re: no icon visual in unity and unity 2d
The package already ships triplane.xpm. I do not use ubuntu and unity does not seem to be in debian yet so I can't easily test this. Is there some spec that should be followed to provide icon for unity in the packaging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922860 Title: no icon visual in unity and unity 2d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/triplane/+bug/922860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876855] Re: Please merge systemtap 1.6-1 (universe) from Debian testing
Yep upstream is still trying to fix some last bugs before 1.7 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876855 Title: Please merge systemtap 1.6-1 (universe) from Debian testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/876855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727160] Re: systemtap process probes requires CONFIG_UTRACE enabled
Sergey, utrace support is not mainline. you need to patch your kernel before you can even select that option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727160 Title: systemtap process probes requires CONFIG_UTRACE enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876855] Re: Please merge systemtap 1.6-1 (universe) from Debian testing
adding-ifdef-CLONE_STOPPED-to-stop-module-compilatio.patch * included upstream since 1.5, can be dropped fix-compile-warning * included upstream since 1.6, can be dropped no-werror.patch * is not needed in debian. are the ubuntu builds done using stricter compiler defaults that cause extra warnings? I don't have ubuntu pbuilder setup right now, only debian so I can't easily test. Updated-__ip_sock_daddr-for-2.6.38-kernels.patch * included upstream since 1.5, can be dropped There are some changes that are not in named patches, I did not investigate those yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876855 Title: Please merge systemtap 1.6-1 (universe) from Debian testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/876855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876855] Re: Please merge systemtap 1.6-1 (universe) from Debian testing
I just heard that upstream 1.7 release is possible happening already next week. you might want to postpone 1.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876855 Title: Please merge systemtap 1.6-1 (universe) from Debian testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/876855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876855] Re: System tap pkg needs a version update
Hi Leo, are you planning to sync systemtap 1.6-1 from debian to ubuntu? If you need to make some ubuntu specific changes it'd be interesting to hear about them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876855 Title: System tap pkg needs a version update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/876855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876855] Re: System tap pkg needs a version update
1.6-1 has been pretty stable for me so far in debian so I agree. Who on the ubuntu side is usually handling such updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876855 Title: System tap pkg needs a version update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/876855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853567] Re: This package is not based on release tar available from github
Marcin, what should we do to this bug? In debian BTS I would mark it as pending but I don't know the launchpad equivalent. Would be you be interested in handling magit bugs that are reported to launchpad? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/853567 Title: This package is not based on release tar available from github To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magit/+bug/853567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853567] Re: This package is not based on release tar available from github
README.source is in git now (800b090142daf41d8342700565132f1feb28921d). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/853567 Title: This package is not based on release tar available from github To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magit/+bug/853567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853567] Re: This package is not based on release tar available from github
They don't match since orig.tar.gz is created from upstream git tag. This should probably be documented in debian/README.source. Reasons included 1) upstream does not sign tarballs so they don't have much extra value 2) having upstream history in Vcs-Git is very useful As git usage patterns for packaging change I'm open at re-evaluating this position. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/853567 Title: This package is not based on release tar available from github To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magit/+bug/853567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
Linus Hoppe, no. It's a bug in foxtrotgps. As Joshua pointed out, we shouldn't be calling xmlCleanupParser like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787953 Title: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
Linus, what do you mean by Status:Invalid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787953 Title: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
Thanks for the report. I work on Debian but here's some information: If I select Start 60.121075,24.460361 End 60.121075,24.460361 Service openrouteservice.org I get do_pickpoint(): close(14) in netlib_connectsock() close(14) in netlib_connectsock() close(14) in netlib_connectsock() close(14) in netlib_connectsock() fetch_track(): 60.121075,24.460361, 60.116558,24.448656 URL ROUTE www.tangogps.org/friends/navtrack.php?service=1start=60.121075,24.460361end=60.116558,24.448656 close(15) in netlib_connectsock() HTTP-GET: size: 24, statuscode 203 noname.xml:1: parser error : Start tag expected, '' not found temporarily out of order ^ Failed to parse document close(14) in netlib_connectsock() close(14) in netlib_connectsock() but no crash (this is foxtrotgps 0.99.4+debian3-3). We have no control over www.tangogps.org. Can you reproduce the crash at will? Could you capture the network traffic between you and www.tangogps.org when that happens so that I could replay it? You can record it without root privileges if you do strace -o foxtrotgps.strace -s4096 -f foxtrotgps and attach the foxtrotgps.strace here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787953 Title: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
The CoreDump.gz that you attached shows at least one occurence of a HTTP reply that has just temporarily out of order in it. I looked at the coredump with gdb. If I go to frame 7 I see that gpx_string contains just temporarily out of order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787953 Title: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
Hmm, www.tangogps.org seems to be down completely now. Can't test the bug anymore :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787953 Title: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
Aha, if I click Ok two times I can also crash foxtrotgps, even on Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787953 Title: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787953] Re: foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
I looked at the disassembly of
void XMLCDECL
xmlGenericErrorDefaultFunc(void *ctx ATTRIBUTE_UNUSED, const char *msg, ...) {
va_list args;
if (xmlGenericErrorContext == NULL)
xmlGenericErrorContext = (void *) stderr;
va_start(args, msg);
vfprintf((FILE *)xmlGenericErrorContext, msg, args);
va_end(args);
}
on amd64. It seems that xmlGenericErrorContext is
(*__xmlGenericErrorContext()) and seems to evaluate differently in the
three calls that are made here. The first two return the same value but
the third returns a different value. This causes vfprintf to get NULL as
the first argument even though the code appears to guard against that.
The implementation has
void * *
__xmlGenericErrorContext(void) {
if (IS_MAIN_THREAD)
return (xmlGenericErrorContext);
else
return (xmlGetGlobalState()-xmlGenericErrorContext);
}
and it seems that IS_MAIN_THREAD evaluates to zero on all three cases.
xmlGetGlobalState(), however, returns first 0x7fffe4019170 and then
0x7fffe4019540. Both have sane data but of course only the first one is
updated to refer to stderr, the second one has xmlGenericErrorContext
set to zero.
xmlGetGlobalState looks very complicated, I can't immediately see why it
would return different value for the same thread during the same
function call.
Anyways, if I apply
diff -u libxml2-2.7.8.dfsg/debian/changelog libxml2-2.7.8.dfsg/debian/changelog
--- libxml2-2.7.8.dfsg/debian/changelog
+++ libxml2-2.7.8.dfsg/debian/changelog
@@ -1,3 +1,9 @@
+libxml2 (2.7.8.dfsg-2lindi0) unstable; urgency=low
+
+ * Try to workaround
https://bugs.launchpad.net/ubuntu/+source/foxtrotgps/+bug/787953
+
+ -- Timo Lindfors li...@kurp.hut.fi Wed, 01 Jun 2011 00:55:10 +0300
+
libxml2 (2.7.8.dfsg-2) unstable; urgency=low
* xpath.c: Fix a double-freeing error in XPath processing code.
only in patch2:
unchanged:
--- libxml2-2.7.8.dfsg.orig/error.c
+++ libxml2-2.7.8.dfsg/error.c
@@ -70,12 +70,13 @@
void XMLCDECL
xmlGenericErrorDefaultFunc(void *ctx ATTRIBUTE_UNUSED, const char *msg, ...) {
va_list args;
+void *errorContext = xmlGenericErrorContext;
-if (xmlGenericErrorContext == NULL)
- xmlGenericErrorContext = (void *) stderr;
+if (errorContext == NULL)
+ errorContext = (void *) stderr;
va_start(args, msg);
-vfprintf((FILE *)xmlGenericErrorContext, msg, args);
+vfprintf((FILE *)errorContext, msg, args);
va_end(args);
}
to libxml2 I do not see the crash anymore.
I doubt the bug is in libxml2 itself but this information might help in
any case. I suspect some threading bug in foxtrotgps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787953
Title:
foxtrotgps crashed with SIGSEGV in ___vfprintf_chk()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599780] [NEW] reproducible crash with free(): invalid pointer
Public bug reported: Binary package hint: xterm Steps to reproduce: 1) start xterm 2) type cat xterm.testcase Expected results: 2) xterm does not crash Actual results: 2) xterm crashes with *** glibc detected *** xterm: free(): invalid pointer: 0x097f5830 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6(+0x6b591)[0xb771d591] /lib/tls/i686/cmov/libc.so.6(+0x6cde8)[0xb771ede8] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0xb7721ecd] xterm[0x8076af7] xterm[0x8077130] xterm[0x8079c24] xterm[0x80821d1] xterm[0x805c251] xterm[0x805fb5f] xterm[0x805fc70] xterm[0x806c200] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb76c8bd6] xterm[0x804d6a1] === Memory map: 08048000-08099000 r-xp 00:10 27821227 /usr/bin/xterm 08099000-0809a000 r--p 0005 00:10 27821227 /usr/bin/xterm 0809a000-080a rw-p 00051000 00:10 27821227 /usr/bin/xterm 080a-080a2000 rw-p 00:00 0 097b7000-098e3000 rw-p 00:00 0 [heap] b6f0-b6f21000 rw-p 00:00 0 b6f21000-b700 ---p 00:00 0 b7046000-b7289000 rw-p 00:00 0 b734a000-b734b000 r-xp 00:10 39346458 /usr/lib/gconv/ISO8859-1.so b734b000-b734c000 r--p 1000 00:10 39346458 /usr/lib/gconv/ISO8859-1.so b734c000-b734d000 rw-p 2000 00:10 39346458 /usr/lib/gconv/ISO8859-1.so b734e000-b736b000 r-xp 00:10 39308646 /lib/libgcc_s.so.1 b736b000-b736c000 r--p 0001c000 00:10 39308646 /lib/libgcc_s.so.1 b736c000-b736d000 rw-p 0001d000 00:10 39308646 /lib/libgcc_s.so.1 b736d000-b7371000 r-xp 00:10 27956029 /usr/lib/libXfixes.so.3.1.0 b7371000-b7372000 r--p 3000 00:10 27956029 /usr/lib/libXfixes.so.3.1.0 b7372000-b7373000 rw-p 4000 00:10 27956029 /usr/lib/libXfixes.so.3.1.0 b7373000-b737b000 r-xp 00:10 27956025 /usr/lib/libXcursor.so.1.0.2 b737b000-b737c000 r--p 7000 00:10 27956025 /usr/lib/libXcursor.so.1.0.2 b737c000-b737d000 rw-p 8000 00:10 27956025 /usr/lib/libXcursor.so.1.0.2 b738e000-b73c5000 r--p 00:10 39343203 /usr/lib/locale/en_US/LC_CTYPE b73c5000-b73ca000 r--p 00:10 39343202 /usr/lib/locale/en_US/LC_COLLATE b73ca000-b73cc000 rw-p 00:00 0 b73cc000-b73cf000 r-xp 00:10 39308706 /lib/libuuid.so.1.3.0 b73cf000-b73d r--p 2000 00:10 39308706 /lib/libuuid.so.1.3.0 b73d-b73d1000 rw-p 3000 00:10 39308706 /lib/libuuid.so.1.3.0 b73d1000-b73d5000 r-xp 00:10 27956027 /usr/lib/libXdmcp.so.6.0.0 b73d5000-b73d6000 r--p 3000 00:10 27956027 /usr/lib/libXdmcp.so.6.0.0 b73d6000-b73d7000 rw-p 4000 00:10 27956027 /usr/lib/libXdmcp.so.6.0.0 b73d7000-b73d9000 r-xp 00:10 27956021 /usr/lib/libXau.so.6.0.0 b73d9000-b73da000 r--p 1000 00:10 27956021 /usr/lib/libXau.so.6.0.0 b73da000-b73db000 rw-p 2000 00:10 27956021 /usr/lib/libXau.so.6.0.0 b73db000-b73dc000 rw-p 00:00 0 b73dc000-b73e3000 r-xp 00:10 27956018 /usr/lib/libSM.so.6.0.1 b73e3000-b73e4000 r--p 6000 00:10 27956018 /usr/lib/libSM.so.6.0.1 b73e4000-b73e5000 rw-p 7000 00:10 27956018 /usr/lib/libSM.so.6.0.1 b73e5000-b73fd000 r-xp 00:10 27956572 /usr/lib/libxcb.so.1.1.0 b73fd000-b73fe000 r--p 00017000 00:10 27956572 /usr/lib/libxcb.so.1.1.0 b73fe000-b73ff000 rw-p 00018000 00:10 27956572 /usr/lib/libxcb.so.1.1.0 b73ff000-b7423000 r-xp 00:10 39308642 /lib/libexpat.so.1.5.2 b7423000-b7425000 r--p 00024000 00:10 39308642 /lib/libexpat.so.1.5.2 b7425000-b7426000 rw-p 00026000 00:10 39308642 /lib/libexpat.so.1.5.2 b7426000-b7439000 r-xp 00:10 39308710 /lib/libz.so.1.2.3.3 b7439000-b743a000 r--p 00012000 00:10 39308710 /lib/libz.so.1.2.3.3 b743a000-b743b000 rw-p 00013000 00:10 39308710 /lib/libz.so.1.2.3.3 b743b000-b743d000 r-xp 00:10 26738713 /lib/tls/i686/cmov/libdl-2.11.1.so b743d000-b743e000 r--p 1000 00:10 26738713 /lib/tls/i686/cmov/libdl-2.11.1.so b743e000-b743f000 rw-p 2000 00:10 26738713 /lib/tls/i686/cmov/libdl-2.11.1.so b743f000-b744 rw-p 00:00 0 b744-b744f000 r-xp 00:10 27956037 /usr/lib/libXpm.so.4.11.0 being printed to .xsession-errors More info: 1) gdb: (gdb) bt full #0 0x002a7422 in __kernel_vsyscall () No symbol table info available. #1 0x002d2651 in raise () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0x002d5a82 in abort () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #3 0x0030949d in ?? () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #4 0x00313591 in ?? () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #5 0x00314de8 in ?? () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #6 0x00317ecd in free () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #7 0x0807f9f1 in addScrollback (screen=0x97c063c) at ../scrollback.c:84 prior = 0x97e4660 where = 0x97e4660 which = 1
[Bug 599780] Re: reproducible crash with free(): invalid pointer
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/5364/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/5365/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/5366/Dependencies.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/5367/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/5368/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/5369/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/5370/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/5371/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/5372/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/5373/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/5374/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/5375/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/5376/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/5377/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/5378/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/5379/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/5380/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/5381/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/5382/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/5383/glxinfo.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/5384/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/5385/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/5386/xkbcomp.txt -- reproducible crash with free(): invalid pointer https://bugs.launchpad.net/bugs/599780 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599780] Re: reproducible crash with free(): invalid pointer
** Attachment added: catting this file crashes xterm. It is sensitive to timing http://launchpadlibrarian.net/5457/xterm.testcase -- reproducible crash with free(): invalid pointer https://bugs.launchpad.net/bugs/599780 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
