*** This bug is a duplicate of bug 330573 ***
https://bugs.launchpad.net/bugs/330573
** This bug has been marked a duplicate of bug 330573
madfuload doesn't work
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug
** Branch linked: lp:~neil-aldur/ubuntu/karmic/madfuload/madfuload-fixes
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Branch unlinked: lp:~neil-aldur/+junk/madfuload
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The debdiff below fixes this fault, the device loading problems and
generally tidies up the package so that it conforms to standards.
** Attachment added: Package update to 2ubuntu3
http://launchpadlibrarian.net/30660604/madfuload_1.2-2ubuntu3.debdiff
--
madfuload crashes with 'segmentation
For those that can't wait, the package for Karmic is available on my
PPA.
https://launchpad.net/~neil-aldur/+archive/ppa
** Changed in: madfuload (Ubuntu)
Assignee: Neil Wilson (neil-aldur) = (unassigned)
--
madfuload crashes with 'segmentation fault' on amd64
** Branch linked: lp:~neil-aldur/+junk/madfuload
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This patch works fine for me, thanks
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this bug
madfuload[3839]: segfault at b4432dc2 ip 7f10b437ac40 sp
7fffbc889aa8 error 4 in libc-2.9.so[7f10b42fa000+168000]
** Changed in: madfuload (Ubuntu)
Status: New = Confirmed
--
madfuload crashes with 'segmentation fault' on amd64
This particular bug is caused by the lack of the correct header
definitions in the C file. The implicit declarations are breaking things
on a 64-bit architecture.
The attached patch will at least get the 'failed to load error' into the
syslog!
Scott - are you happy to package this patch or would
remark to my comment above:
To be more precise: In the output subroutines fatal, warning and logmsg
in madfuload.c the pointer(?) strerror(errno) is converted into a string via
%s,
e.g. in line 289: fatal(cannot claim interface %d: (%d) %s, interface, errno,
strerror(errno)).
I think, this
1) it seems that the seg fault is caused by strerror(errno).
After replacing strerror(errno) with a default text, no segmentation faults
happens anymore.
2) thanks to Strider - Bug #102631 I replaced in the madfuload.rules file
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0,
Scott, this bug is not about the /dev/bus/usb issue, it is about
segfault on amd64.
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I know, my first comment was simply addressing the fact that there was
another problem.
The second comment still stands - the attached patch will not work
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because
Well, the /proc/bus/usb issue simply appears to be that you gave that
path on the command-line no? What happens when you give a /dev/bus/usb
command-line instead?
I've uploaded a fix to the madfuload package udev rules
--
madfuload crashes with 'segmentation fault' on amd64
The attached patch is very incorrect, I can't see what it's trying to do
at all - va_start takes the name of a function argument, and the patch
breaks that
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because
Actually, I take that back. It does look like there is a /proc/bus/usb
issue, but that is separate from the segfault.
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is another bug related to bug #156085
** This bug has been marked a duplicate of bug 156085
Could not open /proc/bus/usb/devices
** This bug is no longer a duplicate of bug 156085
Could not open /proc/bus/usb/devices
--
madfuload crashes with 'segmentation fault' on amd64
exactly. /proc/bus/usb issue exists on both platforms and easily
fixable, but crash happens only on amd64
--
madfuload crashes with 'segmentation fault' on amd64
https://bugs.launchpad.net/bugs/301771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The segmentation fault is caused by the missing usbfs.
While this isn't fixed you can try the following workaround.
Create an entry in /etc/fstab like this:
none/proc/bus/usb usbfs devgid=46,devmode=664 0 0
--
madfuload crashes with 'segmentation fault' on amd64
There is an open bug against madfuload for this very problem, and mr_batschner
seems to have identified where the issue is with a gdb trace:
http://sourceforge.net/tracker2/?func=detailaid=1905613group_id=8atid=584353
There is a patch attached to the bug, but from the bug details, may not
be
dmesg shows this error message on my laptop.
[ 2891.049921] madfuload[11218]: segfault at 53ef1727 ip
7f4e53e3a690 sp 7fff5c3438b8 error 4 in
libc-2.8.90.so[7f4e53db8000+169000]
I have been facing this problem for a while; it used to work fine with
Dapper.
--
madfuload crashes with
21 matches
Mail list logo
