|
From: Jerry L. (lathem) <la...@ci...> - 2008-04-11 20:46:02
|
I am running version 3.3.0 and am getting an abort in valgrind with the above error. I looked in the file ./coregrind/m_syswrap/syswrap-amd64-linux.c and found where the intercepts for get and set of FS are (lines 517-528). My code does a SET_GS which falls into the else clause at line 529. Since valgrind does not need to intercept this, can it just be passed on through to the kernel? I am not familiar enough with the code to write the change, but I am hoping someone can help me. TIA J |
|
From: Jerry L. (lathem) <la...@ci...> - 2008-04-24 18:42:14
|
Is there no-one out there that can help, or did I send to the wrong list? J ________________________________ From: val...@li... [mailto:val...@li...] On Behalf Of Jerry Lathem (lathem) Sent: Friday, April 11, 2008 3:50 PM To: val...@li... Subject: [Valgrind-users] valgrind: the 'impossible' happened: Unsupportedarch_prtctl option I am running version 3.3.0 and am getting an abort in valgrind with the above error. I looked in the file ./coregrind/m_syswrap/syswrap-amd64-linux.c and found where the intercepts for get and set of FS are (lines 517-528). My code does a SET_GS which falls into the else clause at line 529. Since valgrind does not need to intercept this, can it just be passed on through to the kernel? I am not familiar enough with the code to write the change, but I am hoping someone can help me. TIA J |
|
From: Venefax <ve...@gm...> - 2008-04-24 19:58:39
|
I feel your pain. I also found a bug where my app gets killed because valgrind does not understand the Intel multimedia instruction set. -----Original Message----- From: val...@li... [mailto:val...@li...] On Behalf Of Jerry Lathem (lathem) Sent: Thursday, April 24, 2008 2:46 PM To: val...@li... Subject: Re: [Valgrind-users] valgrind: the 'impossible' happened: Unsupportedarch_prtctl option Is there no-one out there that can help, or did I send to the wrong list? J ________________________________ From: val...@li... [mailto:val...@li...] On Behalf Of Jerry Lathem (lathem) Sent: Friday, April 11, 2008 3:50 PM To: val...@li... Subject: [Valgrind-users] valgrind: the 'impossible' happened: Unsupportedarch_prtctl option I am running version 3.3.0 and am getting an abort in valgrind with the above error. I looked in the file ./coregrind/m_syswrap/syswrap-amd64-linux.c and found where the intercepts for get and set of FS are (lines 517-528). My code does a SET_GS which falls into the else clause at line 529. Since valgrind does not need to intercept this, can it just be passed on through to the kernel? I am not familiar enough with the code to write the change, but I am hoping someone can help me. TIA J ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Tom H. <to...@co...> - 2008-04-24 20:45:37
|
In message <000f01c8a645$8ba7bfc0$a2f73f40$@com>
"Venefax" <ve...@gm...> wrote:
> I feel your pain. I also found a bug where my app gets killed because
> valgrind does not understand the Intel multimedia instruction set.
As I said last night, the best thing to do is to file a bug in
bugzilla. You're not likely to get an instant fix though - this
is an open source project and it doesn't have teams of staff
waiting to leap up and do your bidding.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Tom H. <to...@co...> - 2008-04-24 20:45:23
|
In message <D78...@xm...>
"Jerry Lathem (lathem)" <la...@ci...> wrote:
> Is there no-one out there that can help, or did I send to the wrong
> list?
It's the right list, though filing a bug in bugzilla would be even
better if you want to make sure it doesn't get forgotten about.
If you could provide a test case that would be even better - that's
a pretty unusual system call you're using so it might to know what
you're trying to do.
Anything which involves segmentation is complicated and is going
to need careful consideration, so it isn't going to be a case of
just slapping in a pass through I'm afraid - at the very least we
will first need to understand exactly what the call does.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Julian S. <js...@ac...> - 2008-04-24 22:08:28
|
> "Jerry Lathem (lathem)" <la...@ci...> wrote: > > Is there no-one out there that can help, or did I send to the wrong > > list? > > It's the right list, though filing a bug in bugzilla would be even > better if you want to make sure it doesn't get forgotten about. > > If you could provide a test case that would be even better - that's > a pretty unusual system call you're using so it might to know what > you're trying to do. See http://www.valgrind.org/support/bug_reports.html for how to file a report. Just to emphasise what Tom said: your chances of getting a fix in a reasonable amount of time are significantly increased if you include in the report, a simple, self contained program demonstrating the problem. J |