Displaying 20 results from an estimated 76 matches for "sourcefiles".
Did you mean:
sourcefile
2014 Feb 02
1
Trouble implementing ov_callbacks, endless loop calling seek_func
Hello list,
I've been having a tough time adding windows resource support to my ogg
vorbise decoder, although I think I am close. Basically when I call
ov_open_callbacks(), it doesn't ever return and repeatedly calls my
seek_func.
I'm hoping it is something obvious, but I can't see why my seek_func is
being called endlessly. If the file is seekable, I should return 0, right?
If
2014 Feb 02
0
unsubscribe
On 2014-02-02, at 12:00 PM, vorbis-request at xiph.org wrote:
> Send Vorbis mailing list submissions to
> vorbis at xiph.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.xiph.org/mailman/listinfo/vorbis
> or, via email, send a message with subject or body 'help' to
> vorbis-request at xiph.org
>
> You can reach the person
2018 Oct 06
1
TLS handshake failure - Client Helo rejected
Hi,
I can no longer connect to Dovecot (IMAP). The connection is terminated
by Dovecot after Client Helo.
My server:
Dovecot 2.3.3
Debian buster/sid
Architecture: ppc
My problems started in late August after upgrading Dovecot.
SSL settings:
ssl_dh = </etc/ssl/dh2048.pem
ssl_min_protocol = TLSv1.2
ssl_cipher_list =
2005 Aug 28
1
[LLVMdev] how to read the llvm source-file?
I am a new user of the llvm .
where should I to start the llvm -sourcefile.
As there is many tools .What are the most important?
what the order of reading the sourcefile is most efficienc?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050828/ec0bf27e/attachment.html>
2010 Jan 09
4
parsing pdf files
I have a pdf file that I would like to parse into R:
http://www.williams.edu/Registrar/geninfo/faculty.pdf
For now, I open the file in Acrobat by hand, then save it "as text"
and then use readLines(). That works fine but a) I am concerned that
some information may be lost and b) I may be doing this a lot, so I
would rather have R grab the information from the pdf file directly.
So: is
2011 Aug 25
3
Very Basic Source Question
I'm having an issue sourcing an R file from my workbench using StatET in the
Eclipse IDE. All I'm trying to do is get comfortable with 'source' and run
"source(C:/Program Files (x86)/Eclipse/eclipse/ProjectName/SourceFile.R)".
When I try to call the path for the file i get the error: "unexpected '/' in
"source(C:/". I've looked around but
2004 Dec 06
3
[Bug 941] Poor transfer from Windows to Linux
http://bugzilla.mindrot.org/show_bug.cgi?id=941
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From djm at mindrot.org 2004-12-06 17:08
2009 Jul 09
5
[LLVMdev] Source file information.
Dear All,
To add to this, what you want to do is find the appropriate debug stop
point intrinsic and then use it to look up the information for that
instruction.
Here is some sample code from SAFECode that finds the debug information
associated with a CallInst (LLVM call instruction) held in the variable
CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h:
//
// Get the
2009 Nov 04
0
[LLVMdev] Determine branch coverage information
Hi Ahmed!
Adventure wrote:
> Hello everybody, I am a beginner in LLVM and need to know how to use
> LLVM to instrument a C program and execute this instrumented program
> with different test cases to determine the branch coverage information
> for each test case. Any suggestion or help is more than welcomed. Thanks
> in advance. Ahmed Raafat.
(In the following instructions you
2009 Jul 09
0
[LLVMdev] Source file information.
Dear All,
To add to this, what you want to do is find the appropriate debug stop
point intrinsic and then use it to look up the information for that
instruction.
Here is some sample code from SAFECode that finds the debug information
associated with a CallInst (LLVM call instruction) held in the variable
CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h:
//
// Get the
2005 Jun 23
2
hanging pxelinux.0 and menu.c32 on Dell 1850
...ompletely.
I did some research and got it working by using menu.c32 v3.09 and
pxelinux.0 v3.07 -combo.
It seems that from version 3.08 on something has changed on pxelinux.0
file which affects this particular system (Dell 1850).
I think the developers can find the problem by diff'ing correct
sourcefiles so I won't post my config right now.
BR,
-Mikko Kurkela
2003 Aug 24
2
wxRuby 0.1.0 Alpha has been released!
http://rubyforge.org/project/showfiles.php?group_id=35&release_id=46
The code itself has been quite stable for several weeks. This release
includes Gour''s excellent MinGW README notes, along with various updates
to the README, and clarification of the LICENSE.
Thanks to everyone for your help in putting this together. It was
definitely a team project. I look forward to getting lots
2009 Oct 31
2
[LLVMdev] Determine branch coverage information
Hello everybody,
I am a beginner in LLVM and need to know how to use LLVM to instrument a C
program and execute this instrumented program with different test cases to
determine the branch coverage information for each test case.
Any suggestion or help is more than welcomed.
Thanks in advance.
Ahmed Raafat.
--
View this message in context:
2020 Jul 13
2
[PATCH v2 12/24] scsi: virtio_scsi: Demote seemingly unintentional kerneldoc header
This is the only use of kerneldoc in the sourcefile and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd'
drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'buf' not described in
2020 Jul 13
2
[PATCH v2 12/24] scsi: virtio_scsi: Demote seemingly unintentional kerneldoc header
This is the only use of kerneldoc in the sourcefile and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd'
drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'buf' not described in
2010 Jun 01
2
[LLVMdev] How to create global string array? (user question)
I am trying to create such module with API (it's equivalent to c++:
const char* ss[] = {"s1","s2"};):
@ss = global [2 x i8*] [i8* getelementptr inbounds ([3 x i8]* @.str1,
i32 0, i32 0), i8* getelementptr inbounds ([3 x i8]* @.str2, i32 0, i32
0)] ; <[2 x i8*]*> [#uses=0]
@.str1 = private constant [3 x i8] c"s1\00", align 1 ; <[3 x i8]*> [#uses=1]
2003 Sep 30
0
VB Code to convert BMP to LSS for splash screens
The following code can be used to convert a 256 color BMP to LSS format for use as a SYSLINUX/ISOLINUX/PXELINUX Splash screen. The bitmap must be LESS than 640 pixels wide (bug) and only uses the first 16 colors. CorelDraw and PhotoShop are good for re-palletizing and dithering.
Paul Shebanow
pshebanow at iqcorp.com
--- Begin Code ---
Type RGBColor4
cBlue As Byte
cGreen As Byte
2004 Apr 20
8
[Bug 844] the client copy is over written during scp
http://bugzilla.mindrot.org/show_bug.cgi?id=844
Summary: the client copy is over written during scp
Product: Portable OpenSSH
Version: -current
Platform: Other
OS/Version: AIX
Status: NEW
Severity: trivial
Priority: P2
Component: scp
AssignedTo: openssh-bugs at mindrot.org
ReportedBy:
2020 Jul 09
1
[PATCH 12/24] scsi: virtio_scsi: Demote seemingly unintentional kerneldoc header
This is the only use of kerneldoc in the sourcefile and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'vscsi' not described in 'virtscsi_complete_cmd'
drivers/scsi/virtio_scsi.c:109: warning: Function parameter or member 'buf' not described in
2007 Mar 24
1
extracting info from a minidump via winedbg
...00459d3e (0x0022fb58)
12 0x0045b2ee (0x0022fca8)
13 0x0055e77b (0x0022fcf8)
14 0x0055e932 (0x0022fef8)
15 0x0055e483 (0x0022fff0)
16 0x00000000 (0x00000000)
WineDbg starting on pid 068c
Which is pretty rare.
Via addr2line I can translate the backtrace to possibly valid locations in our
sourcefiles.
My questions are:
- Why doesn't winedbg extract the sourcecode locations itself?
- Why doesn't winedbg show me the other information included in the minidump,
like the loaded modules, commandline options or version information?
- How can I get the parameters to the last called function(...