openSUSE Programming June 2012

programming@lists.opensuse.org

5 participants
4 discussions

[opensuse-programming] getting a postfix core dump
by Per Jessen 28 Jun '12

28 Jun '12

I'm trying out this patch: https://build.opensuse.org/package/view_file?file=postfix-mysql-write-suppo… and I keep getting a segfault in proxymap. I've read the postfix DEBUG_README a number of times and tried various debugger_command without getting any closer. I thought the next thing would be getting a core dump, but that's not easy either ... Apparently, there is an issue in getting a core dump from a process that has dropped privileges? I've changed kernel.core_uses_pid and kernel.core_pattern, and I've even tried updating /etc/security/limits.conf, but still no core dump. Any suggestions? -- Per Jessen, Zürich (21.9°C) -- To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-programming+owner(a)opensuse.org

1 0

[opensuse-programming] led display Suppliers shared photos with you
by led display Suppliers 10 Jun '12

10 Jun '12

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

1 0

[opensuse-programming] libusb and LIBUSB_TRANSFER_CANCELLED
by Roger Oberholtzer 07 Jun '12

07 Jun '12

I am experiencing a frustrating problem with a USB device. The device has linux support and uses libusb in asynchronous mode via libusb_fill_interrupt_transfer(). The device is a multi-button device (http://xkeys.com/xkeys/xk24.php). The problem is that, after a random amount of time, the callback registered with libusb_fill_interrupt_transfer() is called with the status LIBUSB_TRANSFER_CANCELLED. There is no need for there to be any user interaction with the device when this happens. It just appears. After this happens, libusb no longer provides any events. In a search, I see some info about this when packets larger than 16k are involved. In the case of this device, the packets are more on the order of 80 bytes. The solution was a newer kernel and libusb. But that was only for devices sending >16k packets. Unfortunately this is on openSUSE 11.2. I cannot update these systems at this time. So I need to see what is happening to see if there is anything I can do. Has anyone come across this kind of behavior on openSUSE? I am using libusb 1.0.2, which seems to be the one that goes with kernel 2.6.31. I have of course asked the supplier. But I get a feeling that may not lead anywhere. The officially support Ubuntu. Support requests seem to disappear. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-programming+owner(a)opensuse.org

1 0

[opensuse-programming] threads and core files
by Roger Oberholtzer 04 Jun '12

04 Jun '12

I have a threaded application that encounters a segmentation violation. I am fairly certain it is the initial thread that encounters the problem. But I just want to be sure of the following: 1. If a multi-threaded app encounters a seg violation, and a core dump is created, the core is of the thread that encountered the seg violation, and not of the main thread, right? 2. If a process starts a thread, and that thread exits, the process does not know about this until it tries to join the thread, right? So, if a thread has a seg violation and exits, the 'parent' thread will also not be made exit. It has to detect the thread is gone by it's own mechanisms or by trying to join the thread. I ask this because I want to be certain I am not misinterpreting which thread in my application is the one that really is getting the seg violation. This is on openSUSE 11.2 with kernel 2.6.31.14-51-desktop Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-programming+owner(a)opensuse.org

5 19

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Programming June 2012